From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/4] rtc: ac100: support clock-output-names in device tree binding
Date: Wed, 31 Aug 2016 18:24:43 +0200 [thread overview]
Message-ID: <20160831162443.idwfr6efztiwtydd@piout.net> (raw)
In-Reply-To: <20160819074226.16636-2-wens@csie.org>
On 19/08/2016 at 15:42:23 +0800, Chen-Yu Tsai wrote :
> The ac100 device tree binding specifies the usage of clock-output-names
> to specify the names of its 3 clock outputs. This is needed for orphan
> clock resolution, when the ac100 is probed much later than any clocks
> that consume any of its outputs. This wasn't supported by the driver.
>
> Add support for this.
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> ---
> Changes since v5:
>
> - New patch, based on mfd-rtc immutable branch given in
>
> http://www.spinics.net/lists/devicetree/msg137991.html
>
> ---
> drivers/rtc/rtc-ac100.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-31 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 7:42 [PATCH v6 0/4] ARM: dts: sun9i: Enable X-Powers AC100 RTC Chen-Yu Tsai
2016-08-19 7:42 ` [PATCH v6 1/4] rtc: ac100: support clock-output-names in device tree binding Chen-Yu Tsai
2016-08-31 16:24 ` Alexandre Belloni [this message]
2016-08-19 7:42 ` [PATCH v6 2/4] ARM: dts: sun9i: a80-optimus: Add device node for AC100 Chen-Yu Tsai
2016-08-19 7:42 ` [PATCH v6 3/4] ARM: dts: sun9i: cubieboard4: " Chen-Yu Tsai
2016-08-19 7:42 ` [PATCH v6 4/4] ARM: dts: sun9i: Switch to the AC100 RTC clock outputs for osc32k Chen-Yu Tsai
2016-08-22 18:40 ` [PATCH v6 0/4] ARM: dts: sun9i: Enable X-Powers AC100 RTC Maxime Ripard
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=20160831162443.idwfr6efztiwtydd@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox