On Fri, Jan 15, 2021 at 10:35:23AM +0000, Richard Fitzgerald wrote:
> On 13/01/2021 16:09, Mark Brown wrote:
> > On Wed, Jan 13, 2021 at 09:22:25AM -0600, Rob Herring wrote:
> some_codec {
> pll: pll {
> compatible = "fixed-clock";
> clocks = <&audio_mclk>;
> clock-frequency = <98304000>;
> }
A PLL is not a fixed clock, why would you define a fixed clock here?
Are you confusing the selection of rates on existing clocks with the use
of the assigned-* properties that the clock binding provides?
> For this to work the clock binding must be a real clock object (so needs
> a valid compatible=). But I need to somehow specify the PLL ID and
That seems like a *very* surprising requirement - why would the clock
binding have that requirement? It would seem to create issues for a
single device providing multiple clocks which should be a pretty common
coase.
> > > > + $ref: /schemas/types.yaml#/definitions/non-unique-string-array
> > > > + description: |
> > > > + A list of clock names giving the source clock for each setting
> > > > + in the sysclks property.
> > > > +
Please delete unneeded context from mails when replying. Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted
material.
Attachment:
signature.asc
Description: PGP signature
