From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: linux-omap@vger.kernel.org,
"U-Boot Mailing List" <u-boot@lists.denx.de>,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, "Stephen Boyd" <sboyd@kernel.org>,
"Tero Kristo" <kristo@kernel.org>,
s-anna@ti.com
Subject: Re: [PATCH] ARM: dts: Use clock-output-names for dra7
Date: Tue, 23 Aug 2022 13:13:31 +0300 [thread overview]
Message-ID: <YwSoSzWBZEGy5UlQ@atomide.com> (raw)
In-Reply-To: <2404bcc0-d01c-1ff1-6ea1-bfdef38cb64e@smile.fr>
* Romain Naour <romain.naour@smile.fr> [220823 08:25]:
> Hello,
>
> Le 04/02/2022 à 09:08, Tony Lindgren a écrit :
> > With the TI clocks supporting the use of clock-output-names devicetree
> > property, we no longer need to use non-standard node names for clocks.
> >
> > Depends-on: 31aa7056bbec ("ARM: dts: Don't use legacy clock defines for dra7 clkctrl")
> > Depends-on: 9206a3af4fc0 ("clk: ti: Move dra7 clock devices out of the legacy section")
> > Cc: Stephen Boyd <sboyd@kernel.org>
> > Cc: Tero Kristo <kristo@kernel.org>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> With this patch applied, u-boot triggers a new warning while applying clock fixup:
>
> ft_fixup_clocks failed for DSP voltage domain: <valid offset/length>
Hmm sounds like u-boot might be automatically syncing to Linux dts files,
and now needs some patching to make use of clock-output-names. The old
non-standard method of relying for node names to get the clock name will
not work as we use generic node names such as "clock".
Regards,
Tony
prev parent reply other threads:[~2022-08-23 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:08 [PATCH] ARM: dts: Use clock-output-names for dra7 Tony Lindgren
2022-08-23 8:32 ` Romain Naour
2022-08-23 10:13 ` Tony Lindgren [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=YwSoSzWBZEGy5UlQ@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=romain.naour@smile.fr \
--cc=s-anna@ti.com \
--cc=sboyd@kernel.org \
--cc=u-boot@lists.denx.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 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).