devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
	k.kozlowski.k@gmail.com, devicetree@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [rtc-linux] [PATCH] rtc: s3c: Document required clocks in the DT binding
Date: Mon, 15 Feb 2016 14:41:10 +0100	[thread overview]
Message-ID: <20160215134110.GA15219@piout.net> (raw)
In-Reply-To: <56C1C95E.7030002@osg.samsung.com>

On 15/02/2016 at 09:49:34 -0300, Javier Martinez Canillas wrote :
> >No, not entirely. The samsung,s3c6410-rtc needs rtc and rtc_src clocks
> >but rest of compatible devices need only rtc clock.
> >
> 
> Right, sorry for missing that. I noticed that this patch has already
> been picked by Rob Herring (I thought it would be picked by Alexandre
> though) so I will post a follow up patch explaining that rtc_src is
> only for the s3c6410-rtc compatible.
> 

Yeah, I was going to take it, thanks for pointing out the Rob already
has it in his tree.


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-02-15 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 17:23 [PATCH] rtc: s3c: Document required clocks in the DT binding Javier Martinez Canillas
     [not found] ` <1455038632-14545-1-git-send-email-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2016-02-14  6:34   ` [rtc-linux] " Krzysztof Kozlowski
     [not found]     ` <56C01FDD.9050204-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-02-15 12:49       ` Javier Martinez Canillas
2016-02-15 13:41         ` Alexandre Belloni [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=20160215134110.GA15219@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=a.zummo@towertech.it \
    --cc=devicetree@vger.kernel.org \
    --cc=javier@osg.samsung.com \
    --cc=k.kozlowski.k@gmail.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).