From: Conor Dooley <conor@kernel.org>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: clock: add support for lan969x
Date: Mon, 16 Sep 2024 16:33:06 +0100 [thread overview]
Message-ID: <20240916-foster-improvise-8019e7e0c023@spud> (raw)
In-Reply-To: <20240916-lan969x-clock-v1-1-0e150336074d@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
On Mon, Sep 16, 2024 at 11:49:19AM +0200, Daniel Machon wrote:
> Lan969x is going to reuse the existing lan966x clock driver - document
> that by adding compatible strings for the different SKU's that we
> support.
>
> Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../devicetree/bindings/clock/microchip,lan966x-gck.yaml | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml b/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
> index df2bec188706..16106e8b637f 100644
> --- a/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
> +++ b/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
> @@ -16,7 +16,18 @@ description: |
>
> properties:
> compatible:
> - const: microchip,lan966x-gck
> + oneOf:
> + - enum:
> + - microchip,lan966x-gck
> + - microchip,lan9691-gck
> + - items:
> + - enum:
> + - microchip,lan9698-gck
> + - microchip,lan9696-gck
> + - microchip,lan9694-gck
> + - microchip,lan9693-gck
> + - microchip,lan9692-gck
> + - const: microchip,lan9691-gck
>
> reg:
> minItems: 1
>
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-16 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 9:49 [PATCH 0/4] clk: lan966x: add support for lan969x SoC clock driver Daniel Machon
2024-09-16 9:49 ` [PATCH 1/4] dt-bindings: clock: add support for lan969x Daniel Machon
2024-09-16 15:33 ` Conor Dooley [this message]
2024-09-16 9:49 ` [PATCH 2/4] clk: lan966x: make clk_names const char * const Daniel Machon
2024-09-16 9:49 ` [PATCH 3/4] clk: lan966x: prepare driver for lan969x support Daniel Machon
2024-09-16 9:49 ` [PATCH 4/4] clk: lan966x: add support for lan969x SoC clock driver Daniel Machon
2024-10-17 22:59 ` [PATCH 0/4] " Stephen Boyd
2024-10-18 8:34 ` claudiu beznea
2024-10-19 6:01 ` Stephen Boyd
2024-10-20 15:39 ` Claudiu Beznea
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=20240916-foster-improvise-8019e7e0c023@spud \
--to=conor@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@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
all inboxes | Powered by JetHome®