From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
rtc-linux@googlegroups.com, devicetree@vger.kernel.org
Subject: Re: [rtc-linux] [PATCH v2] rtc: s3c: Document in binding that only s3c6410 needs a src clk
Date: Tue, 29 Mar 2016 00:19:15 +0200 [thread overview]
Message-ID: <20160328221915.GC2346@piout.net> (raw)
In-Reply-To: <1455545466-25709-1-git-send-email-javier@osg.samsung.com>
On 15/02/2016 at 11:11:06 -0300, Javier Martinez Canillas wrote :
> The S3C binding doc says that the RTC and RTC source clocks are required
> but the S3C driver supports different HW IP and only the s3c6410 needs a
> source clock.
>
> Fix the binding explaining that the source clock is only needed for the
> s3c6410-rtc compatible controller.
>
> Reported-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>
> ---
> Hello,
>
> This patch depends on a previous one that was picked by Rob Herring so
> this one has to go through his tree again and not through the RTC tree
> to avoid conflicts.
>
Well, I'm queuing that one in rtc-fixes for 4.6
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-28 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 14:11 [PATCH v2] rtc: s3c: Document in binding that only s3c6410 needs a src clk Javier Martinez Canillas
2016-02-15 23:22 ` Krzysztof Kozlowski
2016-02-18 14:38 ` Rob Herring
2016-03-17 22:31 ` Alexandre Belloni
2016-03-28 22:19 ` Alexandre Belloni [this message]
2016-04-21 12:46 ` [rtc-linux] " Javier Martinez Canillas
2016-04-21 13:09 ` Alexandre Belloni
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=20160328221915.GC2346@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.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).