From: Marek Vasut <marek.vasut@mailbox.org>
To: Conor Dooley <conor@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, marek.vasut+renesas@mailbox.org
Subject: Re: [PATCH] dt-bindings: clock: rcar-gen2: Remove obsolete header files
Date: Wed, 19 Jun 2024 21:17:28 +0200 [thread overview]
Message-ID: <43a57696-eb4f-4ae3-970a-cee0640baa17@mailbox.org> (raw)
In-Reply-To: <20240619-explain-sip-97568f8ac726@spud>
On 6/19/24 7:48 PM, Conor Dooley wrote:
> On Wed, Jun 19, 2024 at 01:22:46PM +0200, Geert Uytterhoeven wrote:
>> The clock definitions in <dt-bindings/clock/r8a779?-clock.h> were
>> superseded by those in <dt-bindings/clock/r8a779?-cpg-mssr.h> a long
>> time ago.
>>
>> The last DTS user of these files was removed in commit 362b334b17943d84
>> ("ARM: dts: r8a7791: Convert to new CPG/MSSR bindings") in v4.15.
>> Driver support for the old bindings was removed in commit
>> 58256143cff7c2e0 ("clk: renesas: Remove R-Car Gen2 legacy DT clock
>> support") in v5.5, so there is no point to keep on carrying these.
>>
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> If U-Boot is not using them,
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> (and if it is, another task for Marek I guess!)
U-Boot is using upstream DTs on R-Car via OF_UPSTREAM, so whatever
happens in Linux also happens in U-Boot since 2024.07 ... with slight
sync delay . I don't expect much breakage.
Thanks for the heads up !
next prev parent reply other threads:[~2024-06-19 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 11:22 [PATCH] dt-bindings: clock: rcar-gen2: Remove obsolete header files Geert Uytterhoeven
2024-06-19 17:48 ` Conor Dooley
2024-06-19 19:17 ` Marek Vasut [this message]
2024-06-20 8:30 ` Geert Uytterhoeven
2024-06-20 9:06 ` Conor Dooley
2024-07-12 13:19 ` Geert Uytterhoeven
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=43a57696-eb4f-4ae3-970a-cee0640baa17@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).