From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Martin K. Petersen'" <martin.petersen@oracle.com>
Cc: "'Kishon Vijay Abraham I'" <kishon@ti.com>,
"'Vinod Koul'" <vkoul@kernel.org>,
"'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
"'James E . J . Bottomley'" <jejb@linux.ibm.com>,
"'Alim Akhtar'" <alim.akhtar@samsung.com>,
"'Bart Van Assche'" <bvanassche@acm.org>,
<linux-phy@lists.infradead.org>, <linux-scsi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>
Subject: RE: [PATCH v2 0/3] change exynos ufs phy control
Date: Fri, 8 Jul 2022 09:29:08 +0900 [thread overview]
Message-ID: <000a01d89261$bd2c4df0$3784e9d0$@samsung.com> (raw)
In-Reply-To: <yq17d4o624t.fsf@ca-mkp.ca.oracle.com>
> > The first patch is for changing phy clocks manipulation from
> > controlling each symbol/ref clocks to clk_bulk APIs. The second patch
> > is for making power on/off sequences between pmu isolation and clk
> > control. Finally, the third patch changes the phy on/off and init
> > sequences from ufs-exynos host driver.
>
> Were you intending this series to go through SCSI or the phy tree?
I thinks the first two patches are going to phy-tree and you'll need to pick
the last patch.
Vinod,
Could you pick the first two patches in your tree?
Best Regards,
Chanho Park
next prev parent reply other threads:[~2022-07-08 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220706020540epcas2p37a8b697af2c6786db9e4ed67cf20a40f@epcas2p3.samsung.com>
2022-07-06 2:02 ` [PATCH v2 0/3] change exynos ufs phy control Chanho Park
2022-07-06 2:02 ` [PATCH v2 1/3] phy: samsung-ufs: convert phy clk usage to clk_bulk API Chanho Park
2022-07-06 2:02 ` [PATCH v2 2/3] phy: samsung-ufs: ufs: change phy on/off control Chanho Park
2022-07-06 2:02 ` [PATCH v2 3/3] ufs: ufs-exynos: change ufs phy control sequence Chanho Park
2022-07-06 6:56 ` Krzysztof Kozlowski
2022-07-07 21:32 ` [PATCH v2 0/3] change exynos ufs phy control Martin K. Petersen
2022-07-08 0:29 ` Chanho Park [this message]
2022-07-08 5:09 ` Vinod Koul
2022-07-19 3:08 ` Martin K. Petersen
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='000a01d89261$bd2c4df0$3784e9d0$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vkoul@kernel.org \
/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