From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>,
"'Alim Akhtar'" <alim.akhtar@samsung.com>,
"'James E . J . Bottomley'" <jejb@linux.ibm.com>,
"'Martin K . Petersen'" <martin.petersen@oracle.com>,
"'Krzysztof Kozlowski'" <krzysztof.kozlowski@canonical.com>
Cc: "'Bean Huo'" <beanhuo@micron.com>,
"'Bart Van Assche'" <bvanassche@acm.org>,
"'Adrian Hunter'" <adrian.hunter@intel.com>, <hch@infradead.org>,
"'Can Guo'" <cang@codeaurora.org>,
"'Jaegeuk Kim'" <jaegeuk@kernel.org>,
"'Jaehoon Chung'" <jh80.chung@samsung.com>,
"'Gyunghoon Kwon'" <goodjob.kwon@samsung.com>,
"'Sowon Na'" <sowon.na@samsung.com>,
<linux-samsung-soc@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
"'Kiwoong Kim'" <kwmad.kim@samsung.com>
Subject: RE: [PATCH v4 07/16] scsi: ufs: ufs-exynos: correct timeout value setting registers
Date: Fri, 15 Oct 2021 18:53:25 +0900 [thread overview]
Message-ID: <000e01d7c1aa$7f3b9010$7db2b030$@samsung.com> (raw)
In-Reply-To: <DM6PR04MB65752FCA8B8CDF2E0BA0988FFCB89@DM6PR04MB6575.namprd04.prod.outlook.com>
Hi, Thanks for your review.
> -----Original Message-----
> From: Avri Altman <Avri.Altman@wdc.com>
> Sent: Thursday, October 14, 2021 9:12 PM
> To: Chanho Park <chanho61.park@samsung.com>; Alim Akhtar
> <alim.akhtar@samsung.com>; James E . J . Bottomley <jejb@linux.ibm.com>;
> Martin K . Petersen <martin.petersen@oracle.com>; Krzysztof Kozlowski
> <krzysztof.kozlowski@canonical.com>
> Cc: Bean Huo <beanhuo@micron.com>; Bart Van Assche <bvanassche@acm.org>;
> Adrian Hunter <adrian.hunter@intel.com>; hch@infradead.org; Can Guo
> <cang@codeaurora.org>; Jaegeuk Kim <jaegeuk@kernel.org>; Jaehoon Chung
> <jh80.chung@samsung.com>; Gyunghoon Kwon <goodjob.kwon@samsung.com>; Sowon
> Na <sowon.na@samsung.com>; linux-samsung-soc@vger.kernel.org; linux-
> scsi@vger.kernel.org; Kiwoong Kim <kwmad.kim@samsung.com>
> Subject: RE: [PATCH v4 07/16] scsi: ufs: ufs-exynos: correct timeout value
> setting registers
>
> >
> > PA_PWRMODEUSERDATA0 -> DL_FC0PROTTIMEOUTVAL
> > PA_PWRMODEUSERDATA1 -> DL_TC0REPLAYTIMEOUTVAL
> > PA_PWRMODEUSERDATA2 -> DL_AFC0REQTIMEOUTVAL
> Is there a specific reason why this fix is part of the exynosauto series?
I found the issue when I made the patches with some refactoring of ufs-exynos driver.
I can send it separately.
Best Regards,
Chanho Park
next prev parent reply other threads:[~2021-10-15 9:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211007081133epcas2p31f973709609d82dbbc76bd7b51232cb2@epcas2p3.samsung.com>
2021-10-07 8:09 ` [PATCH v4 00/16] introduce exynosauto v9 ufs driver Chanho Park
2021-10-07 8:09 ` [PATCH v4 01/16] scsi: ufs: add quirk to handle broken UIC command Chanho Park
2021-10-14 10:48 ` Avri Altman
2021-10-07 8:09 ` [PATCH v4 02/16] scsi: ufs: add quirk to enable host controller without ph configuration Chanho Park
2021-10-14 10:49 ` Avri Altman
2021-10-07 8:09 ` [PATCH v4 03/16] scsi: ufs: ufs-exynos: change pclk available max value Chanho Park
2021-10-07 8:09 ` [PATCH v4 04/16] scsi: ufs: ufs-exynos: simplify drv_data retrieval Chanho Park
2021-10-07 8:09 ` [PATCH v4 05/16] scsi: ufs: ufs-exynos: add refclkout_stop control Chanho Park
2021-10-07 8:09 ` [PATCH v4 06/16] scsi: ufs: ufs-exynos: add setup_clocks callback Chanho Park
2021-10-07 8:09 ` [PATCH v4 07/16] scsi: ufs: ufs-exynos: correct timeout value setting registers Chanho Park
2021-10-14 12:12 ` Avri Altman
2021-10-15 9:53 ` Chanho Park [this message]
2021-10-07 8:09 ` [PATCH v4 08/16] scsi: ufs: ufs-exynos: support custom version of ufs_hba_variant_ops Chanho Park
2021-10-07 8:09 ` [PATCH v4 09/16] scsi: ufs: ufs-exynos: add EXYNOS_UFS_OPT_SKIP_CONFIG_PHY_ATTR option Chanho Park
2021-10-07 8:09 ` [PATCH v4 10/16] scsi: ufs: ufs-exynos: factor out priv data init Chanho Park
2021-10-07 8:09 ` [PATCH v4 11/16] scsi: ufs: ufs-exynos: add pre/post_hce_enable drv callbacks Chanho Park
2021-10-07 8:09 ` [PATCH v4 12/16] scsi: ufs: ufs-exynos: support exynosauto v9 ufs driver Chanho Park
2021-10-07 8:09 ` [PATCH v4 13/16] dt-bindings: ufs: exynos-ufs: add io-coherency property Chanho Park
2021-10-15 13:50 ` Rob Herring
2021-10-18 0:26 ` Chanho Park
2021-10-18 13:23 ` Rob Herring
2021-10-18 11:07 ` Chanho Park
2021-10-07 8:09 ` [PATCH v4 14/16] scsi: ufs: ufs-exynos: multi-host configuration for exynosauto Chanho Park
2021-10-14 18:51 ` Avri Altman
2021-10-15 11:44 ` Chanho Park
2021-10-18 5:34 ` Inki Dae
2021-10-07 8:09 ` [PATCH v4 15/16] scsi: ufs: ufs-exynos: introduce exynosauto v9 virtual host Chanho Park
2021-10-14 19:03 ` Avri Altman
2021-10-15 12:13 ` Chanho Park
2021-10-07 8:09 ` [PATCH v4 16/16] dt-bindings: ufs: exynos-ufs: add exynosautov9 compatible Chanho Park
2021-10-14 10:04 ` [PATCH v4 00/16] introduce exynosauto v9 ufs driver Avri Altman
2021-10-15 11:57 ` Chanho Park
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='000e01d7c1aa$7f3b9010$7db2b030$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=goodjob.kwon@samsung.com \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jh80.chung@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sowon.na@samsung.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