devicetree.vger.kernel.org archive mirror
 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, devicetree@vger.kernel.org,
	kgene.kim@samsung.com, Prathyush K <prathyush.k@samsung.com>
Subject: Re: [PATCH 1/1] ARM: EXYNOS: Add enable property to power domains
Date: Sun, 10 Nov 2013 20:06:45 +0100	[thread overview]
Message-ID: <1646520.A0KuNSviNZ@flatron> (raw)
In-Reply-To: <1383806575-28401-1-git-send-email-sachin.kamat@linaro.org>

Hi Sachin,

On Thursday 07 of November 2013 12:12:55 Sachin Kamat wrote:
> From: Prathyush K <prathyush.k@samsung.com>
> 
> Different power domains of Exynos SOCs have different enable values.
> E.g. Exynos5250:
> ROTATOR_MEM_CONFIGURATION -> 0x3
> GSCL_CONFIGURATION -> 0x7
> Currently, there is no way to differentiate between these power domains
> and we write default value of 0x7 to turn on all the power domains.
> 
> This patch adds a new 'enable' property to the power domain structure.
> This enable value can be set from the device tree by adding a property
> 'enable' in the device node. If no such property is found, the default
> value of 0x7 is used as enable value.

Is this patch really needed? Is there any problem with simply using 0x7?
Patch description should always include rationale behind the change.

> 
> Signed-off-by: Prathyush K <prathyush.k@samsung.com>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> ---
>  .../bindings/arm/exynos/power_domain.txt           |    5 +++++
>  arch/arm/mach-exynos/pm_domains.c                  |   10 +++++++---
>  2 files changed, 12 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/exynos/power_domain.txt b/Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> index 5216b419016a..6b24b234617c 100644
> --- a/Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> +++ b/Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> @@ -9,6 +9,10 @@ Required Properties:
>  - reg: physical base address of the controller and length of memory mapped
>      region.
>  
> +Optional Properties:
> +- enable: enable value of the register which is used to turn on the power
> +    domain. If no enable is specificed, default value of 0x7 is used.

Vendor-specific properties should have vendor prefix added, so this one
should be called samsung,enable instead. Also enable is not a very
specific name.

So in the end, if it turns out that we really need such patch, I'd prefer
something like:

- samsung,enable-bit-mask: Mask of power control register bits that need
    to be set to enable the power domain. If omitted, it defaults to 0x7.

Best regards,
Tomasz

  reply	other threads:[~2013-11-10 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  6:42 [PATCH 1/1] ARM: EXYNOS: Add enable property to power domains Sachin Kamat
2013-11-10 19:06 ` Tomasz Figa [this message]
     [not found] <1B.DE.05666.EC070825@epcpsbgx2.samsung.com>
2013-11-11 14:28 ` Tomasz Figa
2013-11-12 13:21   ` Bartlomiej Zolnierkiewicz

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=1646520.A0KuNSviNZ@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=prathyush.k@samsung.com \
    --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 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).