RE: [PATCH v5] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed

[Fang Hongjie(方洪杰)]

> From: Bean Huo [mailto:beanhuo@xxxxxxxx]
> Sent: Wednesday, May 6, 2026 8:44 PM
> To: Bart Van Assche <bvanassche@xxxxxxx>; Fang Hongjie(方洪杰)
> <hongjiefang@xxxxxxxxxxxx>; alim.akhtar@xxxxxxxxxxx;
> avri.altman@xxxxxxx; James.Bottomley@xxxxxxxxxxxxxxxxxxxxx;
> martin.petersen@xxxxxxxxxx
> Cc: linux-scsi@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> can.guo@xxxxxxxxxxxxxxxx
> Subject: Re: [PATCH v5] scsi: ufs: core: call hibern8 notify when hibern8 cmd
> failed
> 
> On Wed, 2026-05-06 at 11:16 +0200, Bart Van Assche wrote:
> > On 5/6/26 10:47 AM, Bean Huo wrote:
> > > Thanks for the explanation. However, the kernel development practice is
> to
> > > not
> > > merge infrastructure without at least one in-tree user. Please resubmit
> this
> > > patch together with your platform driver (or at least the hibern8_notify
> > > callback that handles ROLLBACK_CHANGE) so reviewers can verify the
> design is
> > > correct and actually works as intended.
> > >
> > > @Bart, any idea?
> >
> > Everyone who works on Android smartphones has to deal with the
> following:
> > - The upstream-first policy.
> > - Not disclosing any aspect of the phone under development until it has
> >    been announced publicly.
> >
> > Typically two years elapse between the start of testing kernel code for
> > a new phone and public announcement. Another 1 - 4 years elapse after
> > a phone has been announced until all kernel code for a smartphone is
> > upstream. Insisting on not merging any code upstream until a user for
> > the code is upstream makes the job of smartphone kernel developers
> > harder than necessary.
> >
> > This is why I'm fine with deviating from the rule explained in your
> > email for small changes.
> >
> > Thanks,
> >
> > Bart.
> 
> 
> Thanks Bart.
> 
> 
> @Fang Hongjie,
> 
> I respect the practical constraints Bart described, but my concern is about
> design validation, not disclosure. Could you at least show a minimal
> hibern8_notify handler that uses ROLLBACK_CHANGE?
> 
> It doesn't need to be the full platform driver, just enough to demonstrate
> what
> "rollback" means concretely (e.g., undo clock gating, restore PHY state, etc.).
> Without that, we're merging an API whose semantics are unverifiable.
> 
> Especially, other vendors (SS, Qcom, MTK, etc.) should be able to see the
> direction and understand whether they also need to handle
> ROLLBACK_CHANGE in
> their own hibern8_notify callbacks.
> 
> Otherwise, please include this patch as part of your platform driver patch
> series when you submit it, so reviewers can evaluate the infrastructure and
> its consumer together.
> 

We have discovered that on our new platform, the UIC error interrupt must be
temporarily disabled when entering or exiting hibern8; otherwise,
it will interfere with the execution of the hibern8 command itself.
Of course, this is merely a specific corner-case limitation in the controller
design and has no impact on data transmission. Due to this limitation, 
the UIC error must be re-enabled regardless of whether the hibern8 command
executes successfully, as failure to do so will affect the monitoring of the
actual UIC errors during subsequent data transmission.


> Kind Regards,
> Bean


Best.