From: Stephen Boyd <sboyd@kernel.org>
To: Alexander Dahl <ada@thorsis.com>, linux-clk@vger.kernel.org
Cc: u.kleine-koenig@pengutronix.de,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v2] dt-bindings: clk: Make example a bit clearer
Date: Fri, 08 Nov 2019 14:18:42 -0800 [thread overview]
Message-ID: <20191108221843.2600820865@mail.kernel.org> (raw)
In-Reply-To: <2819678.zAmqMVPImI@ada>
Quoting Alexander Dahl (2019-10-10 07:16:00)
>
> > If anything, I would clarify the description of
> > the example by indicating what parts of the example we're talking about
> > when explaining, i.e.
> >
> > In this example the <&pll 2> clock is set as parent of the
> > <&clkcon 0> clock because the first clock specifier in the
> > assigned-clocks property is <&clkcon 0> and that matches the
> > first clock specifier in the assigned-clock-parents property.
> > Similarly the <&pll 2> clock is assigned a frequency value of
> > 460800 Hz because the second frequency in the
> > assigned-clock-rates property is 460800 Hz and that matches the
> > second clock specifier in the assigned-clocks property <&pll 2>.
>
> I could go with that and send a v3 with the obfuscation from above (I'd like
> to keep that) and this paragraph of yours?
>
Sure. Please resend.
prev parent reply other threads:[~2019-11-08 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 10:03 [PATCH v2] dt-bindings: clk: Make example a bit clearer Alexander Dahl
2019-09-11 16:06 ` Stephen Boyd
2019-09-11 16:06 ` Stephen Boyd
2019-09-11 17:49 ` Uwe Kleine-König
2019-09-11 17:49 ` Uwe Kleine-König
2019-09-16 20:13 ` Stephen Boyd
2019-10-10 14:16 ` Alexander Dahl
2019-11-08 22:18 ` 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=20191108221843.2600820865@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=ada@thorsis.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.