From: devarsh <devarsht@ti.com>
To: Vinod Koul <vkoul@kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
<kishon@kernel.org>
Cc: <linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
Parth Pancholi <parth.pancholi@toradex.com>,
Francesco Dolcini <francesco@dolcini.it>,
Aradhya Bhatia <aradhya.bhatia@linux.dev>,
Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH 0/2] phy: cdns-dphy: hs-clk improvement and a cleanup
Date: Tue, 12 Aug 2025 11:32:17 +0530 [thread overview]
Message-ID: <cac3d853-11aa-481b-90bb-aeb2cd4608f8@ti.com> (raw)
In-Reply-To: <aJM0WPVDUkte9E_D@vaman>
Hi Vinod, Kishon,
On 06/08/25 16:24, Vinod Koul wrote:
> On 05-08-25, 15:03, Tomi Valkeinen wrote:
>> Hi Vinod, Kishon,
>>
>> On 23/07/2025 13:01, Tomi Valkeinen wrote:
>>> A cdns-dphy improvement to return the actual hs clock rate, and a
>>> cleanup to remove leftover code.
>>>
>>> These were part of a Cadence DSI series:
>>>
>>> https://lore.kernel.org/all/20250618-cdns-dsi-impro-v4-0-862c841dbe02%40ideasonboard.com/
>>>
>>> but are now separately here for easier merging.
>>>
>>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>>> ---
>>> Tomi Valkeinen (2):
>>> phy: cdns-dphy: Store hs_clk_rate and return it
>>> phy: cdns-dphy: Remove leftover code
>>>
>>> drivers/phy/cadence/cdns-dphy.c | 24 +++++++++---------------
>>> 1 file changed, 9 insertions(+), 15 deletions(-)
>>> ---
>>> base-commit: 89be9a83ccf1f88522317ce02f854f30d6115c41
>>> change-id: 20250723-cdns-dphy-hs-clk-rate-fix-a8857a5789dd
>>
>> Is this good to merge, and if so, do you have any estimate when? While
>> this is independent from the DSI series, I'd rather push the DSI series
>> into drm-misc about the same time, so both would appear in linux-next
>> relatively together.
>
> I will start taking patches after merge window closes next monday, so
> next week should be a good estimate
On top of this series [1], we have the cadence DPHY fixes for fixing PLL
lockup timeout [2] and one more patch which enables lower resolutions
[3], both have been reviewed and tested too.
Would it be possible for you too merge all 3 together in below order ?
[1]:
https://lore.kernel.org/all/cc0e4cf5-1bd9-4ae3-a130-0483dbfc6335@ideasonboard.com/
[2]: https://lore.kernel.org/all/20250704125915.1224738-1-devarsht@ti.com/
[3]: https://lore.kernel.org/all/20250807052002.717807-1-h-shenoy@ti.com/
Kindly let us know if anything required from our side.
Regards
Devarsh
next prev parent reply other threads:[~2025-08-12 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 10:01 Tomi Valkeinen
2025-07-23 10:01 ` [PATCH 1/2] phy: cdns-dphy: Store hs_clk_rate and return it Tomi Valkeinen
2025-07-23 10:01 ` [PATCH 2/2] phy: cdns-dphy: Remove leftover code Tomi Valkeinen
2025-08-05 12:03 ` [PATCH 0/2] phy: cdns-dphy: hs-clk improvement and a cleanup Tomi Valkeinen
2025-08-06 10:54 ` Vinod Koul
2025-08-12 6:02 ` devarsh [this message]
2025-08-18 13:05 ` Devarsh Thakkar
2025-08-12 16:41 ` Vinod Koul
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=cac3d853-11aa-481b-90bb-aeb2cd4608f8@ti.com \
--to=devarsht@ti.com \
--cc=aradhya.bhatia@linux.dev \
--cc=francesco@dolcini.it \
--cc=j-choudhary@ti.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=parth.pancholi@toradex.com \
--cc=tomi.valkeinen@ideasonboard.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
all inboxes | Powered by JetHome®