From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 1/2] dt-bindings: clock: document the fsl-sai driver
Date: Thu, 5 Dec 2019 09:16:48 -0600 [thread overview]
Message-ID: <20191205151648.GA5680@bogus> (raw)
In-Reply-To: <20191122235622.8818-1-michael@walle.cc>
On Sat, Nov 23, 2019 at 12:56:21AM +0100, Michael Walle wrote:
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> .../bindings/clock/fsl,sai-clock.yaml | 48 +++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml
>
> diff --git a/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml b/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml
> new file mode 100644
> index 000000000000..7116c8bc24d3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml
> @@ -0,0 +1,48 @@
> +# SPDX-License-Identifier: GPL-2.0
Dual license new bindings please: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bindings/clock/fsl,sai-clock.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Freescale SAI bitclock-as-a-clock binding
> +
> +maintainers:
> + - Michael Walle <michael@walle.cc>
> +
> +description: |
> + It is possible to use the BCLK pin of a SAI module as a generic clock
> + output. Some SoC are very constrained in their pin multiplexer
> + configuration. Eg. pins can only be changed groups. For example, on the
> + LS1028A SoC you can only enable SAIs in pairs. If you use only one SAI,
> + the second pins are wasted. Using this binding it is possible to use the
> + clock of the second SAI as a MCLK clock for an audio codec, for example.
> +
> + This is a composite of a gated clock and a divider clock.
> +
> +properties:
> + compatible:
> + const: fsl,vf610-sai-clock
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + '#clock-cells':
> + const: 0
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - '#clock-cells'
> +
Add:
additionalProperties: false
> +examples:
> + - |
> + mclk: clock-mclk@f130080 {
> + compatible = "fsl,vf610-sai-clock";
> + reg = <0x0 0xf130080 0x0 0x80>;
Examples are built now and this will fail because the default
#address-cells and #size-cells are 1.
> + #clock-cells = <0>;
> + clocks = <&parentclk>;
> + };
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-12-05 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 23:56 [PATCH 1/2] dt-bindings: clock: document the fsl-sai driver Michael Walle
2019-11-22 23:56 ` [PATCH 2/2] clk: fsl-sai: new driver Michael Walle
2019-12-02 21:46 ` Michael Walle
2019-12-05 15:16 ` Rob Herring [this message]
2019-12-06 1:23 ` [PATCH 1/2] dt-bindings: clock: document the fsl-sai driver Michael Walle
2019-12-09 23:36 ` Michael Walle
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=20191205151648.GA5680@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael@walle.cc \
--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).