From: Conor Dooley <conor@kernel.org>
To: "Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] clk: marvell: Move number of clocks to driver source
Date: Sun, 13 Aug 2023 10:45:30 +0100 [thread overview]
Message-ID: <20230813-accuracy-constrict-fe6fe41c8b4e@spud> (raw)
In-Reply-To: <20230812-mmp-nr-clks-v2-0-f9271bd7eaa5@skole.hr>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
On Sat, Aug 12, 2023 at 12:02:55PM +0200, Duje Mihanović wrote:
> Hi,
>
> In v4 of my PXA1908 series, Conor suggested that the NR_CLKS variables
> in dt bindings should be moved to the respective driver source files
> because these are not used by the device trees and so are needlessly
> added to the ABI. This series does that for the rest of the Marvell
> PXA/MMP SoCs.
>
> Link: https://lore.kernel.org/r/20230808-produce-thievish-3ce1b86a114b@spud/
> Signed-off-by: Duje Mihanović <duje.mihanovic@skole.hr>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
conor.
> ---
> Changes in v2:
> - Fix clk-audio.c compile error
> - Reword mmp2 commit to match other commits
> - Link to v1: https://lore.kernel.org/r/20230809-mmp-nr-clks-v1-0-5f3cdbbb89b8@skole.hr
>
> ---
> Duje Mihanović (4):
> clk: mmp2: Move number of clocks to driver source
> clk: pxa168: Move number of clocks to driver source
> clk: pxa1928: Move number of clocks to driver source
> clk: pxa910: Move number of clocks to driver source
>
> drivers/clk/mmp/clk-audio.c | 6 ++++--
> drivers/clk/mmp/clk-of-mmp2.c | 4 +++-
> drivers/clk/mmp/clk-of-pxa168.c | 4 +++-
> drivers/clk/mmp/clk-of-pxa1928.c | 7 +++++--
> drivers/clk/mmp/clk-of-pxa910.c | 4 +++-
> include/dt-bindings/clock/marvell,mmp2-audio.h | 1 -
> include/dt-bindings/clock/marvell,mmp2.h | 1 -
> include/dt-bindings/clock/marvell,pxa168.h | 1 -
> include/dt-bindings/clock/marvell,pxa1928.h | 3 ---
> include/dt-bindings/clock/marvell,pxa910.h | 1 -
> 10 files changed, 18 insertions(+), 14 deletions(-)
> ---
> base-commit: 52a93d39b17dc7eb98b6aa3edb93943248e03b2f
> change-id: 20230809-mmp-nr-clks-7c80e416e6bf
>
> Best regards,
> --
> Duje Mihanović <duje.mihanovic@skole.hr>
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-08-13 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 10:02 [PATCH v2 0/4] clk: marvell: Move number of clocks to driver source Duje Mihanović
2023-08-12 10:02 ` [PATCH v2 1/4] clk: mmp2: " Duje Mihanović
2023-08-22 21:14 ` Stephen Boyd
2023-08-12 10:02 ` [PATCH v2 2/4] clk: pxa168: " Duje Mihanović
2023-08-22 21:14 ` Stephen Boyd
2023-08-12 10:02 ` [PATCH v2 3/4] clk: pxa1928: " Duje Mihanović
2023-08-22 21:15 ` Stephen Boyd
2023-08-12 10:02 ` [PATCH v2 4/4] clk: pxa910: " Duje Mihanović
2023-08-22 21:15 ` Stephen Boyd
2023-08-13 9:45 ` Conor Dooley [this message]
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=20230813-accuracy-constrict-fe6fe41c8b4e@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=duje.mihanovic@skole.hr \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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).