From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<robh+dt@kernel.org>, <nicolas.ferre@microchip.com>,
<kavyasree.kotagiri@microchip.com>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [RFC PATCH v2 1/3] dt-bindings: clock: lan966x: Extend for clock gate support
Date: Fri, 29 Oct 2021 14:19:27 +0200 [thread overview]
Message-ID: <20211029121929.2811811-2-horatiu.vultur@microchip.com> (raw)
In-Reply-To: <20211029121929.2811811-1-horatiu.vultur@microchip.com>
Allow to add an optional resource to be able to access the clock gate
registers.
Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
---
.../devicetree/bindings/clock/microchip,lan966x-gck.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml b/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
index fca83bd68e26..a53c889629da 100644
--- a/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
+++ b/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
@@ -19,7 +19,8 @@ properties:
const: microchip,lan966x-gck
reg:
- maxItems: 1
+ minItems: 1
+ maxItems: 2
clocks:
items:
--
2.33.0
next prev parent reply other threads:[~2021-10-29 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 12:19 [RFC PATCH v2 0/3] Extend lan966x clock driver for clock gating support Horatiu Vultur
2021-10-29 12:19 ` Horatiu Vultur [this message]
2021-10-29 12:19 ` [RFC PATCH v2 2/3] dt-bindings: clock: lan966x: Extend includes with clock gates Horatiu Vultur
2021-10-29 12:19 ` [RFC PATCH v2 3/3] clk: lan966x: Extend lan966x clock driver for clock gating support Horatiu Vultur
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=20211029121929.2811811-2-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.