All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Tero Kristo" <kristo@kernel.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH 0/4] Use reg instead of ti,bit-shift for clksel
Date: Thu, 29 Feb 2024 09:06:26 +0200	[thread overview]
Message-ID: <20240229070626.GH52537@atomide.com> (raw)
In-Reply-To: <20240214054044.GK52537@atomide.com>

* Tony Lindgren <tony@atomide.com> [240214 05:41]:
> * Andreas Kemnade <andreas@kemnade.info> [240213 23:11]:
> > On Tue, 13 Feb 2024 12:56:40 +0200
> > Tony Lindgren <tony@atomide.com> wrote:
> > 
> > > Hi all,
> > > 
> > > This series updates the clksel clocks to use the standard reg property
> > > instead of ti,bit-shift.
> > > 
> > > I'd like to apply these before we make further use of the clksel clocks
> > > to reduce the dtb check warnings.
> > > 
> > 
> > hmm, we still have ti,bit-shift if these clocks are not used below a ti,clksel.
> > Just wondering, can we completely deorbit ti,bit-shift if we used #address-cells = <2>;
> > in those cases? I wait a bit with further txt->yaml conversions until
> > this is settled.
> 
> No need to wait on the yaml conversion I think :) How about just tag the
> ti,bit-shift property as deprecated? And add a comment saying it is only
> needed for the remaining unconnected clocks.
> 
> Eventually we can move all the component clocks under clksel clocks, or the
> related clock such as the dpll clock for the clkdcoldo clocks.

Oh and yes, using #clock-cells = <2> would be nice eventually :) I think
the clkcel binding already supports that. But that still leaves the issue
of unconnected composite clocks.. I'm pretty sure they all have some real
parent like clksel for dpll though.

If you had some good idea in mind for the #address-cells = <2> for the
remaining unconnected composite clocks maybe clarify it a bit.

Regards,

Tony

  reply	other threads:[~2024-02-29  7:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 10:56 [PATCH 0/4] Use reg instead of ti,bit-shift for clksel Tony Lindgren
2024-02-13 10:56 ` [PATCH 1/4] clk: ti: Handle possible address in the node name Tony Lindgren
2024-02-22  5:11   ` Stephen Boyd
2024-02-13 10:56 ` [PATCH 2/4] clk: ti: Improve clksel clock bit parsing for reg property Tony Lindgren
2024-02-22  5:11   ` Stephen Boyd
2024-02-13 10:56 ` [PATCH 3/4] ARM: dts: am3: Update clksel clocks to use reg instead of ti,bit-shift Tony Lindgren
2024-02-13 10:56 ` [PATCH 4/4] ARM: dts: omap3: " Tony Lindgren
2024-02-13 23:11 ` [PATCH 0/4] Use reg instead of ti,bit-shift for clksel Andreas Kemnade
2024-02-14  5:40   ` Tony Lindgren
2024-02-29  7:06     ` Tony Lindgren [this message]
2024-03-02 19:18       ` Andreas Kemnade
2024-03-08  9:00         ` Tony Lindgren

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=20240229070626.GH52537@atomide.com \
    --to=tony@atomide.com \
    --cc=andreas@kemnade.info \
    --cc=bcousson@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.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.