From: Vignesh Raghavendra <vigneshr@ti.com>
To: Alim Akhtar <alim.akhtar@samsung.com>,
"'Alim Akhtar'" <alim.akhtar@gmail.com>,
"'sheebab'" <sheebab@cadence.com>
Cc: "'Avri Altman'" <avri.altman@wdc.com>,
"'Pedro Sousa'" <pedrom.sousa@synopsys.com>,
"'James E.J. Bottomley'" <jejb@linux.ibm.com>,
"'Martin K. Petersen'" <martin.petersen@oracle.com>,
"'Stanley Chu'" <stanley.chu@mediatek.com>,
"'Bean Huo (beanhuo)'" <beanhuo@micron.com>,
<yuehaibing@huawei.com>, <linux-scsi@vger.kernel.org>,
"'open list'" <linux-kernel@vger.kernel.org>,
<linux-block@vger.kernel.org>, <rafalc@cadence.com>,
<mparab@cadence.com>
Subject: Re: [PATCH RESEND 2/2] scsi: ufs: Update L4 attributes on manual hibern8 exit in Cadence UFS.
Date: Wed, 27 Nov 2019 09:45:45 +0530 [thread overview]
Message-ID: <69e16181-e01c-1120-2074-80b9c1eb19ce@ti.com> (raw)
In-Reply-To: <08c701d5a4d4$b20c7300$16255900$@samsung.com>
Hi Alim,
On 27/11/19 9:12 AM, Alim Akhtar wrote:
>
[...]
>>>> Backup L4 attributes duirng manual hibern8 entry and restore the L4
>>>> attributes on manual hibern8 exit as per JESD220C.
>>>>
>>> Can you point me to the relevant section on the spec?
>>>
>>
>> Per JESD 220C 9.4 UniPro/UFS Control Interface (Control Plane):
>>
>> "NOTE After exit from Hibernate all UniPro Transport Layer attributes (including
>> L4 T_PeerDeviceID,
>>
>> L4 T_PeerCPortID, L4 T_ConnectionState, etc.) will be reset to their reset values.
>> All required attributes
>>
>> must be restored properly on both ends before communication can resume."
>>
>> But its not clear whether SW needs to restore these attributes or hardware
>>
> Thanks Vignesh for pointing out the spec section, yes it is not clear, one way to confirm this is just by read L4 attributes before
> And after hinern8 entry/exit.
I know that on Cadence UFS controller L4 attributes are definitely lost
on hibernation entry/exit and therefore needs to be restored. But not
sure of other controllers. If this issue is seen on other controllers as
well, then we should probably consider moving this code to core driver
so that there is code reuse.
> (at least in the current platform it is not being done)
> AFA this patch is concerns, this looks ok to me.
> @ Avri , any thought on this?
>
>> Regards
>> Vignesh
>>
[...]
--
Regards
Vignesh
next prev parent reply other threads:[~2019-11-27 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 7:04 [PATCH RESEND 0/2] scsi: ufs: hibern8 fixes sheebab
2019-11-19 7:04 ` [PATCH RESEND 1/2] scsi: ufs: Enable hibern8 interrupt only during manual hibern8 in Cadence UFS sheebab
2019-11-19 7:04 ` [PATCH RESEND 2/2] scsi: ufs: Update L4 attributes on manual hibern8 exit " sheebab
2019-11-20 16:20 ` Alim Akhtar
2019-11-21 10:56 ` Vignesh Raghavendra
2019-11-27 3:42 ` Alim Akhtar
2019-11-27 4:15 ` Vignesh Raghavendra [this message]
2019-11-27 15:18 ` Avri Altman
2019-11-28 13:59 ` Alim Akhtar
2019-11-22 11:44 ` [PATCH RESEND 0/2] scsi: ufs: hibern8 fixes Vignesh Raghavendra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69e16181-e01c-1120-2074-80b9c1eb19ce@ti.com \
--to=vigneshr@ti.com \
--cc=alim.akhtar@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mparab@cadence.com \
--cc=pedrom.sousa@synopsys.com \
--cc=rafalc@cadence.com \
--cc=sheebab@cadence.com \
--cc=stanley.chu@mediatek.com \
--cc=yuehaibing@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox