devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	bcousson@baylibre.com, linux-arm-kernel@lists.infradead.org,
	hns@goldelico.com
Subject: Re: [PATCH] ARM: dts: omap3-beagle-xm: Add fixed 26MHz clock as fck for twl
Date: Tue, 1 May 2018 08:18:16 -0700	[thread overview]
Message-ID: <20180501151816.GM5671@atomide.com> (raw)
In-Reply-To: <065d346a-12a4-3dc6-d8a3-e5351a73a7ab@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [180406 07:01]:
> 
> 
> On 2018-04-05 16:15, Peter Ujfalusi wrote:
> > 
> > 
> > On 2018-04-05 14:52, Peter Ujfalusi wrote:
> >> The board uses 26MHz oscillator for the twl4030 HFCLK.
> >> This way we will not depend on the bootloader to configure the
> >> CFG_BOOT:HFCLK_FREQ
> >>
> >> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> >> ---
> >> Hi,
> >>
> >> there might be other boards (all omap3 boards with twl4030?) which uses the same
> >> setup, but I only have schematics for beagle-xm.
> >>
> >> In order for the driver to actually use the clock the 
> >> [PATCH] mfd: twl-core: Fix clock initialization
> >> need to be applied. W/o the twl-core patch the clock is just ignored.
> >>
> >> Regards,
> >> Peter
> >>
> >>  arch/arm/boot/dts/omap3-beagle-xm.dts | 10 ++++++++++
> >>  1 file changed, 10 insertions(+)
> >>
> >> diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts b/arch/arm/boot/dts/omap3-beagle-xm.dts
> >> index 0349fcc9dc26..d80587de0bbf 100644
> >> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
> >> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
> >> @@ -30,6 +30,13 @@
> >>  		ethernet = &ethernet;
> >>  	};
> >>  
> >> +	/* fixed 26MHz oscillator */
> >> +	hfclk_26m: oscillator {
> >> +		#clock-cells = <0>;
> >> +		compatible = "fixed-clock";
> >> +		clock-frequency = <26000000>;
> >> +	};
> >> +
> >>  	leds {
> >>  		compatible = "gpio-leds";
> >>  
> >> @@ -274,6 +281,9 @@
> >>  		interrupts = <7>; /* SYS_NIRQ cascaded to intc */
> >>  		interrupt-parent = <&intc>;
> >>  
> >> +		clocks = <&hfclk_26m>;
> >> +		clock-names = "fck";
> > 
> > I wonder if we should rename this to hfclk...
> > The DT documentation does not mention it and afaik it is not specified
> > in DT files either.
> > 
> > After all it is the HFCLK clock for the twl4030.
> 
> We should not as it would break compatibility with stable kernels where
> the code expects 'fck' and not hfclk.

OK applying into omap-for-v4.18/dt thanks.

Tony

  reply	other threads:[~2018-05-01 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 11:52 [PATCH] ARM: dts: omap3-beagle-xm: Add fixed 26MHz clock as fck for twl Peter Ujfalusi
2018-04-05 13:15 ` Peter Ujfalusi
2018-04-06  7:00   ` Peter Ujfalusi
2018-05-01 15:18     ` Tony Lindgren [this message]
2018-05-01 15:30 ` Adam Ford
2018-05-01 15:39   ` 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=20180501151816.GM5671@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    /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).