All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, kgene.kim@samsung.com,
	patches@linaro.org, mturquette@linaro.org, inki.dae@samsung.com
Subject: Re: [PATCH 2/3] of/documentation: Update G2D documentation
Date: Sat, 06 Jul 2013 01:52:48 +0200	[thread overview]
Message-ID: <4264635.Hmig5l0VLj@flatron> (raw)
In-Reply-To: <1373013749-14530-2-git-send-email-sachin.kamat@linaro.org>

Hi Sachin,

On Friday 05 of July 2013 14:12:28 Sachin Kamat wrote:
> Exynos5250 G2D IP requires only the gate clock. Update the
> binding documentation accordingly.
> 
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> Cc: Inki Dae <inki.dae@samsung.com>
> ---
>  .../devicetree/bindings/gpu/samsung-g2d.txt        |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/gpu/samsung-g2d.txt
> b/Documentation/devicetree/bindings/gpu/samsung-g2d.txt index
> 3f454ff..60ca631 100644
> --- a/Documentation/devicetree/bindings/gpu/samsung-g2d.txt
> +++ b/Documentation/devicetree/bindings/gpu/samsung-g2d.txt
> @@ -12,7 +12,9 @@ Required properties:
>    - interrupts : G2D interrupt number to the CPU.
>    - clocks : from common clock binding: handle to G2D clocks.
>    - clock-names : from common clock binding: must contain "sclk_fimg2d"
> and -		  "fimg2d", corresponding to entries in the clocks 
property. +		
>  "fimg2d" for S5PV210 & Exynos4 based SoCs and "fimg2d" for +		 
> Exynos5250 SoC, corresponding to entries in the clocks
> +		  property.

I think this needs to be rephrased, because I can't get any sense from 
this sentence.

Maybe something like:

- clock-names : names of clocks listed in clocks property, in the same 
order, depending on SoC type:
    - for S5PV210 and Exynos4 based SoCs : "fimg2d" and "sclk_fimg2d"
    - for Exynos5250 SoC : "fimg2d".

What do you think?

Best regards,
Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] of/documentation: Update G2D documentation
Date: Sat, 06 Jul 2013 01:52:48 +0200	[thread overview]
Message-ID: <4264635.Hmig5l0VLj@flatron> (raw)
In-Reply-To: <1373013749-14530-2-git-send-email-sachin.kamat@linaro.org>

Hi Sachin,

On Friday 05 of July 2013 14:12:28 Sachin Kamat wrote:
> Exynos5250 G2D IP requires only the gate clock. Update the
> binding documentation accordingly.
> 
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> Cc: Inki Dae <inki.dae@samsung.com>
> ---
>  .../devicetree/bindings/gpu/samsung-g2d.txt        |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/gpu/samsung-g2d.txt
> b/Documentation/devicetree/bindings/gpu/samsung-g2d.txt index
> 3f454ff..60ca631 100644
> --- a/Documentation/devicetree/bindings/gpu/samsung-g2d.txt
> +++ b/Documentation/devicetree/bindings/gpu/samsung-g2d.txt
> @@ -12,7 +12,9 @@ Required properties:
>    - interrupts : G2D interrupt number to the CPU.
>    - clocks : from common clock binding: handle to G2D clocks.
>    - clock-names : from common clock binding: must contain "sclk_fimg2d"
> and -		  "fimg2d", corresponding to entries in the clocks 
property. +		
>  "fimg2d" for S5PV210 & Exynos4 based SoCs and "fimg2d" for +		 
> Exynos5250 SoC, corresponding to entries in the clocks
> +		  property.

I think this needs to be rephrased, because I can't get any sense from 
this sentence.

Maybe something like:

- clock-names : names of clocks listed in clocks property, in the same 
order, depending on SoC type:
    - for S5PV210 and Exynos4 based SoCs : "fimg2d" and "sclk_fimg2d"
    - for Exynos5250 SoC : "fimg2d".

What do you think?

Best regards,
Tomasz

  reply	other threads:[~2013-07-05 23:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05  8:42 [PATCH 1/3] clk: exynos5250: Add G2D gate clock Sachin Kamat
2013-07-05  8:42 ` Sachin Kamat
2013-07-05  8:42 ` [PATCH 2/3] of/documentation: Update G2D documentation Sachin Kamat
2013-07-05  8:42   ` Sachin Kamat
2013-07-05 23:52   ` Tomasz Figa [this message]
2013-07-05 23:52     ` Tomasz Figa
2013-07-08  6:36     ` Sachin Kamat
2013-07-08  6:36       ` Sachin Kamat
2013-07-05  8:42 ` [PATCH 3/3] ARM: EXYNOS: Add G2D support to exynos5250 Sachin Kamat
2013-07-05  8:42   ` Sachin Kamat
2013-07-31  5:52   ` Kukjin Kim
2013-07-31  5:52     ` Kukjin Kim
2013-07-26  8:48 ` [PATCH 1/3] clk: exynos5250: Add G2D gate clock Sachin Kamat
2013-07-26  8:48   ` Sachin Kamat
2013-07-26 20:18 ` Mike Turquette
2013-07-26 20:18   ` Mike Turquette
2013-07-27 13:29   ` Sachin Kamat
2013-07-27 13:29     ` Sachin Kamat
2013-07-30  6:48     ` Mike Turquette
2013-07-30  6:48       ` Mike Turquette
2013-07-30  6:55       ` Sachin Kamat
2013-07-30  6:55         ` Sachin Kamat
2013-07-31  3:42         ` Mike Turquette
2013-07-31  3:42           ` Mike Turquette
2013-07-31  3:48           ` Sachin Kamat
2013-07-31  3:48             ` Sachin Kamat

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=4264635.Hmig5l0VLj@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=inki.dae@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=patches@linaro.org \
    --cc=sachin.kamat@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.