All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Marek Vasut <marex@denx.de>, linux-clk@vger.kernel.org
Cc: devicetree@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: clk: rs9: Add Renesas 9-series I2C PCIe clock generator
Date: Thu, 17 Feb 2022 17:28:16 -0800	[thread overview]
Message-ID: <20220218012817.EA554C340E8@smtp.kernel.org> (raw)
In-Reply-To: <7605efbd-1a5e-ef80-5638-8376a325e3ba@denx.de>

Quoting Marek Vasut (2022-02-17 17:09:26)
> On 2/18/22 00:39, Stephen Boyd wrote:
> > Quoting Marek Vasut (2022-02-13 09:33:09)
> >> diff --git a/Documentation/devicetree/bindings/clock/renesas,9series.yaml b/Documentation/devicetree/bindings/clock/renesas,9series.yaml
> >> new file mode 100644
> >> index 0000000000000..774053748d9f0
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/clock/renesas,9series.yaml
> >> @@ -0,0 +1,102 @@
> >> +required:
> >> +  - compatible
> >> +  - reg
> >> +  - '#clock-cells'
> > 
> > Can it operate without an input xtal?
> 
> Not to my knowledge.
> 

Ok please make it required property then.

      reply	other threads:[~2022-02-18  1:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 17:33 [PATCH 1/2] dt-bindings: clk: rs9: Add Renesas 9-series I2C PCIe clock generator Marek Vasut
2022-02-13 17:33 ` [PATCH 2/2] clk: rs9: Add Renesas 9-series PCIe clock generator driver Marek Vasut
2022-02-17 23:45   ` Stephen Boyd
2022-02-18  1:26     ` Marek Vasut
2022-02-18 22:15       ` Stephen Boyd
2022-02-19  1:11         ` Marek Vasut
2022-02-19  3:05           ` Stephen Boyd
2022-02-19  3:27             ` Marek Vasut
2022-02-17 23:39 ` [PATCH 1/2] dt-bindings: clk: rs9: Add Renesas 9-series I2C PCIe clock generator Stephen Boyd
2022-02-18  1:09   ` Marek Vasut
2022-02-18  1:28     ` Stephen Boyd [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=20220218012817.EA554C340E8@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@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.