From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: sheebab <sheebab@cadence.com>
Cc: <alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<pedrom.sousa@synopsys.com>, <vigneshr@ti.com>,
<linux-block@vger.kernel.org>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <stanley.chu@mediatek.com>,
<beanhuo@micron.com>, <yuehaibing@huawei.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rafalc@cadence.com>, <mparab@cadence.com>
Subject: Re: [PATCH RESEND 0/2] scsi: ufs: hibern8 fixes
Date: Mon, 18 Nov 2019 23:36:58 -0500 [thread overview]
Message-ID: <yq1eey4jxcl.fsf@oracle.com> (raw)
In-Reply-To: <1573815645-11886-1-git-send-email-sheebab@cadence.com> (sheebab@cadence.com's message of "Fri, 15 Nov 2019 16:30:43 +0530")
sheebab,
> Resending this patch to include 'mailing list' which I missed in first
> release.
>
> This patch set contains following patches for Cadence UFS controller
> driver.
>
> 1. 0001-scsi-ufs-Enable-hibern8-interrupt-only-during-manual.patch
> This patch is to fix false interrupt assertion during auto hibernation.
> In this patch, hibern8 interrupt is Disabled during initialization
> and later the interrupt is Enabled/Disabled during manual hibern8
> Entry/Exit.
> 2. 0002-scsi-ufs-Update-L4-attributes-on-manual-hibern8-exit.patch
> This patch is to update L4 attributes during manual hibern8 exit.
> As per JESD220C spec, L4 attributes will be reset to their reset value
> during DME_HIBERNATION_EXIT. This patch will take backup of the L4
> parameters before DME_HIBERNATION_ENTER and restores the L4 parameters
> after DME_HIBERNATION_EXIT
Only the cover letter made it to the list. Please make sure patch
submissions are sent to linux-scsi@vger.kernel.org.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-11-19 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 11:00 [PATCH RESEND 0/2] scsi: ufs: hibern8 fixes sheebab
2019-11-19 4:36 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-19 7:04 sheebab
2019-11-22 11:44 ` 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=yq1eey4jxcl.fsf@oracle.com \
--to=martin.petersen@oracle.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=mparab@cadence.com \
--cc=pedrom.sousa@synopsys.com \
--cc=rafalc@cadence.com \
--cc=sheebab@cadence.com \
--cc=stanley.chu@mediatek.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.