From: Bean Huo <huobean@gmail.com>
To: Chanho Park <chanho61.park@samsung.com>,
'Krzysztof Kozlowski' <krzk@kernel.org>,
'Alim Akhtar' <alim.akhtar@samsung.com>,
"'James E . J . Bottomley'" <jejb@linux.ibm.com>,
"'Martin K . Petersen'" <martin.petersen@oracle.com>
Cc: 'Can Guo' <cang@codeaurora.org>,
'Jaegeuk Kim' <jaegeuk@kernel.org>,
'Kiwoong Kim' <kwmad.kim@samsung.com>,
'Avri Altman' <avri.altman@wdc.com>,
'Adrian Hunter' <adrian.hunter@intel.com>,
'Christoph Hellwig' <hch@infradead.org>,
'Bart Van Assche' <bvanassche@acm.org>,
'jongmin jeong' <jjmin.jeong@samsung.com>,
'Gyunghoon Kwon' <goodjob.kwon@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 14/15] scsi: ufs: ufs-exynos: multi-host configuration for exynosauto
Date: Tue, 27 Jul 2021 21:36:05 +0200 [thread overview]
Message-ID: <8af01dbdfbecf2aa2f35e8c3a5240b2bcf76d9b0.camel@gmail.com> (raw)
In-Reply-To: <004601d782d0$2f43cd20$8dcb6760$@samsung.com>
On Tue, 2021-07-27 at 19:14 +0900, Chanho Park wrote:
> > > A PH has its own doorbell register and each VHs also has it as
> > > well.
> > > The TASK_TAG[7:5] can be used to distinguish the origin of the
> > > request among VHs and remaining TASK_TAG[4:0] will be used for
> > > supporting 32 tags.
> > > Best Regards,
> > > Chanho Park
> > Thanks for your reply.
> > so you split the "Task Tag" filed byte3 in the UPIU header to two
> > parts, bit7~bit5 is for the VHs ID, and bit4~bit0 is for the task
> > ID.
> > but this is not defined in the Spec 2.1. correct?
>
>
> You're right.
>
> For PH, TASK_TAG[7:5] will be set to "0" but a VHID will be used in
> case of VH.
>
>
>
> Best Regards,
>
> Chanho Park
Hi Chanho Park,
Thansk for yoru reply.
I didn't see your changes about task_tag and IID. Having a look at
ufshcd_prepare_utp_scsi_cmd_upiu(), the task tag in the UPIU header
is still only task tag. and IID is always 0x00.
If you didn't add these changes, your patch is un-readable, and also
the driver doesn't have a real usage case.
Also, you mentioned there is no support/change needed from the UFS
device side. But, IMO, if you changed the UPIU header, there are
changes needed on the UFS device side in order to use your driver.
Kind regards,
Bean
next prev parent reply other threads:[~2021-07-27 19:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210714071158epcas2p1a7b98fd67b9bcaaa634e59fc224761b1@epcas2p1.samsung.com>
2021-07-14 7:11 ` [PATCH v2 00/15] introduce exynosauto v9 ufs driver Chanho Park
[not found] ` <CGME20210714071158epcas2p261e6c9157056fafca0f55aaf05cd68ef@epcas2p2.samsung.com>
2021-07-14 7:11 ` [PATCH v2 01/15] scsi: ufs: add quirk to handle broken UIC command Chanho Park
[not found] ` <CGME20210714071158epcas2p29900b577a489b760a1e67eba976fb815@epcas2p2.samsung.com>
2021-07-14 7:11 ` [PATCH v2 02/15] scsi: ufs: add quirk to enable host controller without ph configuration Chanho Park
[not found] ` <CGME20210714071159epcas2p36dc12e150a84ef4fa2516bc98169725b@epcas2p3.samsung.com>
2021-07-14 7:11 ` [PATCH v2 03/15] scsi: ufs: ufs-exynos: change pclk available max value Chanho Park
[not found] ` <CGME20210714071159epcas2p3fa23ac2a670e1c31deeac1c9332f76fe@epcas2p3.samsung.com>
2021-07-14 7:11 ` [PATCH v2 04/15] scsi: ufs: ufs-exynos: simplify drv_data retrieval Chanho Park
[not found] ` <CGME20210714071159epcas2p2ae981fb3b91b0eba23060de5de104ec0@epcas2p2.samsung.com>
2021-07-14 7:11 ` [PATCH v2 05/15] scsi: ufs: ufs-exynos: get sysreg regmap for io-coherency Chanho Park
[not found] ` <CGME20210714071159epcas2p3d39f7e5cbd9a2b8addaa496a396213af@epcas2p3.samsung.com>
2021-07-14 7:11 ` [PATCH v2 06/15] scsi: ufs: ufs-exynos: add refclkout_stop control Chanho Park
[not found] ` <CGME20210714071159epcas2p4c4eabf50abdaa46567fc5356bce8942b@epcas2p4.samsung.com>
2021-07-14 7:11 ` [PATCH v2 07/15] scsi: ufs: ufs-exynos: add setup_clocks callback Chanho Park
[not found] ` <CGME20210714071159epcas2p24b7be0cad31af09bc71c608f9b03fe36@epcas2p2.samsung.com>
2021-07-14 7:11 ` [PATCH v2 08/15] scsi: ufs: ufs-exynos: correct timeout value setting registers Chanho Park
[not found] ` <CGME20210714071159epcas2p4edc8104aad36d4d7a5bedb8328c0ab39@epcas2p4.samsung.com>
2021-07-14 7:11 ` [PATCH v2 09/15] scsi: ufs: ufs-exynos: support custom version of ufs_hba_variant_ops Chanho Park
[not found] ` <CGME20210714071159epcas2p24323976939fa21a5ed44d81649b33d85@epcas2p2.samsung.com>
2021-07-14 7:11 ` [PATCH v2 10/15] scsi: ufs: ufs-exynos: add EXYNOS_UFS_OPT_SKIP_CONFIG_PHY_ATTR option Chanho Park
[not found] ` <CGME20210714071159epcas2p176be9a1310f8de27cfb3786fe86630d6@epcas2p1.samsung.com>
2021-07-14 7:11 ` [PATCH v2 11/15] scsi: ufs: ufs-exynos: factor out priv data init Chanho Park
[not found] ` <CGME20210714071159epcas2p428292c7d0e97533de65d92a029eece93@epcas2p4.samsung.com>
2021-07-14 7:11 ` [PATCH v2 12/15] scsi: ufs: ufs-exynos: add pre/post_hce_enable drv callbacks Chanho Park
[not found] ` <CGME20210714071200epcas2p199f4f7b209e565c9a87440af319acda1@epcas2p1.samsung.com>
2021-07-14 7:11 ` [PATCH v2 13/15] scsi: ufs: ufs-exynos: support exynosauto v9 ufs driver Chanho Park
[not found] ` <CGME20210714071200epcas2p3f76e68f6bbb4755574dba2055a8130ab@epcas2p3.samsung.com>
2021-07-14 7:11 ` [PATCH v2 14/15] scsi: ufs: ufs-exynos: multi-host configuration for exynosauto Chanho Park
2021-07-26 9:08 ` Bean Huo
2021-07-26 10:40 ` Chanho Park
2021-07-26 21:58 ` Bean Huo
2021-07-27 10:14 ` Chanho Park
2021-07-27 19:36 ` Bean Huo [this message]
2021-07-28 1:39 ` Chanho Park
2021-07-29 21:10 ` Bean Huo
2021-07-26 22:06 ` Bean Huo
2021-07-27 9:05 ` Chanho Park
[not found] ` <CGME20210714071200epcas2p413ca643dc459ee75ec7e5e4f8a6c05d7@epcas2p4.samsung.com>
2021-07-14 7:11 ` [PATCH v2 15/15] scsi: ufs: ufs-exynos: introduce exynosauto v9 virtual host 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=8af01dbdfbecf2aa2f35e8c3a5240b2bcf76d9b0.camel@gmail.com \
--to=huobean@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=chanho61.park@samsung.com \
--cc=goodjob.kwon@samsung.com \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jjmin.jeong@samsung.com \
--cc=krzk@kernel.org \
--cc=kwmad.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).