public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-clk@vger.kernel.org, sboyd@kernel.org,
	mturquette@baylibre.com, linux-omap@vger.kernel.org,
	jsarha@ti.com
Subject: Re: [PATCH 0/3] clk: ti: add CLK_SET_RATE_PARENT support for clkctrl
Date: Mon, 26 Feb 2018 14:05:20 -0800	[thread overview]
Message-ID: <20180226220520.GI16043@atomide.com> (raw)
In-Reply-To: <1519657812-15605-1-git-send-email-t-kristo@ti.com>

Hi,

* Tero Kristo <t-kristo@ti.com> [180226 15:11]:
> This patch adds clock rate propagation support for clkctrl clocks. This
> is needed on am33xx beaglebone black device at least, otherwise the
> display does not work. Similar problem appears to be present on am43xx
> but haven't heard of any reports of such so far, maybe Jyri can confirm
> this?

I think I was also hitting this with the system timers with ti-sysc
where set_parent() would fail unless the dts has the following for
timers:

clocks = <&l4_wkup_clkctrl OMAP4_TIMER1_CLKCTRL 24>;

So bit 24 instead of 0.

Hmm so should we have all the timers use bit 0 in the dtsi?
Or default to bit 24 for all of them?

Regards,

Tony

  parent reply	other threads:[~2018-02-26 22:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 15:10 [PATCH 0/3] clk: ti: add CLK_SET_RATE_PARENT support for clkctrl Tero Kristo
2018-02-26 15:10 ` [PATCH 1/3] clk: ti: clkctrl: add support for CLK_SET_RATE_PARENT flag Tero Kristo
2018-02-26 15:10 ` [PATCH 2/3] clk: ti: am33xx: add set-rate-parent support for display clkctrl clock Tero Kristo
2018-02-26 15:10 ` [PATCH 3/3] clk: ti: am43xx: " Tero Kristo
2018-02-26 22:05 ` Tony Lindgren [this message]
2018-02-27  6:34   ` [PATCH 0/3] clk: ti: add CLK_SET_RATE_PARENT support for clkctrl Tero Kristo
2018-02-27 16:42     ` Tony Lindgren
2018-02-27 16:48       ` Tony Lindgren
2018-02-28  5:37         ` Tero Kristo
2018-02-28 21:58           ` Tony Lindgren
2018-03-01  7:04             ` Tero Kristo
2018-03-01 15:26               ` Tony Lindgren
2018-02-28 10:23 ` Jyri Sarha

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=20180226220520.GI16043@atomide.com \
    --to=tony@atomide.com \
    --cc=jsarha@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=t-kristo@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