From: Tomasz Figa <tomasz.figa@gmail.com>
To: Leela Krishna Amudala <l.krishna@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
wim@iguana.be, t.figa@samsung.com, devicetree@vger.kernel.org,
dianders@chromium.org, linux-watchdog@vger.kernel.org,
cpgs@samsung.com, sachin.kamat@linaro.org
Subject: Re: [PATCH V8 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files
Date: Sat, 16 Nov 2013 00:43:19 +0100 [thread overview]
Message-ID: <1736135.JdedDOBENL@flatron> (raw)
In-Reply-To: <1384238088-9862-2-git-send-email-l.krishna@samsung.com>
On Tuesday 12 of November 2013 12:04:46 Leela Krishna Amudala wrote:
> This patch adds pmusysreg node to exynos5250 and exynos5420 dtsi files to
> handle PMU register accesses in a centralized way using syscon driver
>
> Signed-off-by: Leela Krishna Amudala <l.krishna@samsung.com>
> Reviewed-by: Tomasz Figa <t.figa@samsung.com>
> ---
> Documentation/devicetree/bindings/arm/samsung/pmu.txt | 13 +++++++++++++
> arch/arm/boot/dts/exynos5250.dtsi | 5 +++++
> arch/arm/boot/dts/exynos5420.dtsi | 5 +++++
> 3 files changed, 23 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/samsung/pmu.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> new file mode 100644
> index 0000000..90f975d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> @@ -0,0 +1,13 @@
> +SAMSUNG Exynos SoC series PMU Registers
> +
> +Properties:
> + - name : should be 'syscon';
> + - compatible : should contain "samsung,<chip name>-pmu", "syscon";
AFAIR there was a discussion about using <chip name> wildcards some
time ago and if I remember correctly, the conclusion was that the list
of all supported compatible values should be provided anyway, so there
is no point in using such wildcards.
This is how I would write this:
- compatible : should contain two values. First value must be one from
following list:
- "samsung,exynos5250-pmu" - for Exynos5250 SoC,
- "samsung,exynos5420-pmu" - for Exynos5420 SoC.
Second value must be always "syscon".
Best regards,
Tomasz
next prev parent reply other threads:[~2013-11-15 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 6:34 [PATCH V8 0/3] Add watchdog DT nodes and use syscon regmap interfac to configure pmu registers Leela Krishna Amudala
2013-11-12 6:34 ` [PATCH V8 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files Leela Krishna Amudala
2013-11-15 23:43 ` Tomasz Figa [this message]
2013-11-18 9:17 ` Leela Krishna Amudala
2013-11-12 6:34 ` [PATCH V8 2/3] watchdog: s3c2410_wdt: add device tree support and use syscon regmap interface to configure pmu register Leela Krishna Amudala
2013-11-15 2:49 ` Guenter Roeck
2013-11-15 23:57 ` Tomasz Figa
2013-11-18 9:24 ` Leela Krishna Amudala
2013-11-12 6:34 ` [PATCH V8 3/3] ARM: dts: update watchdog device nodes for Exynos5250 and Exynos5420 Leela Krishna Amudala
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=1736135.JdedDOBENL@flatron \
--to=tomasz.figa@gmail.com \
--cc=cpgs@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=l.krishna@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.com \
--cc=wim@iguana.be \
/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).