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: 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: [PATCH] rtc: s3c: Document in binding that only s3c6410 needs a src clk
Date: Mon, 15 Feb 2016 14:45:35 +0100	[thread overview]
Message-ID: <20160215134535.GB15219@piout.net> (raw)
In-Reply-To: <1455542202-13977-1-git-send-email-javier@osg.samsung.com>

On 15/02/2016 at 10:16:42 -0300, Javier Martinez Canillas wrote :
> Commit 43f3408261a2 ("rtc: s3c: Document required clocks in the DT

I'm pretty sure you shouldn't refer to a commit that is in linux-next.

> binding") added to the S3C binding doc the required clocks needed
> by the Real Time Clock but the S3C driver supports different HW IP
> and only the s3c6410 needs a source clock.
> 
> Fix the DT binding explaning that the second clock is only needed
          explaining ^
> by this IP block and not for the others.
> 
> Reported-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Fixes: 43f3408261a2 ("rtc: s3c: Document required clocks in the DT binding")
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> 

Anyway, I'm fine with it, feel free to add my ack.

> ---
> Hello,
> 
> The mentioned commit was picked by Rob Herring so this one has to go
> through his tree again and not through the RTC tree to avoid conflicts.
> 
> Best regards,
> Javier
> 
>  Documentation/devicetree/bindings/rtc/s3c-rtc.txt | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/rtc/s3c-rtc.txt b/Documentation/devicetree/bindings/rtc/s3c-rtc.txt
> index 1068ffce9f91..fdde63a5419c 100644
> --- a/Documentation/devicetree/bindings/rtc/s3c-rtc.txt
> +++ b/Documentation/devicetree/bindings/rtc/s3c-rtc.txt
> @@ -15,9 +15,10 @@ Required properties:
>    is the rtc tick interrupt. The number of cells representing a interrupt
>    depends on the parent interrupt controller.
>  - clocks: Must contain a list of phandle and clock specifier for the rtc
> -          and source clocks.
> -- clock-names: Must contain "rtc" and "rtc_src" entries sorted in the
> -               same order as the clocks property.
> +          clock and in the case of a s3c6410 compatible controller, also
> +          a source clock.
> +- clock-names: Must contain "rtc" and for a s3c6410 compatible controller,
> +               a "rtc_src" sorted in the same order as the clocks property.
>  
>  Example:
>  
> -- 
> 2.5.0
> 

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

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 13:16 [PATCH] rtc: s3c: Document in binding that only s3c6410 needs a src clk Javier Martinez Canillas
2016-02-15 13:45 ` Alexandre Belloni [this message]
2016-02-15 13:58   ` Javier Martinez Canillas

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=20160215134535.GB15219@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).