From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/7] Documentation: Add device tree bindings for Freescale i.MX GPC
Date: Tue, 18 Feb 2014 19:10:03 +0100 [thread overview]
Message-ID: <2328803.HhaG6blXIR@wuerfel> (raw)
In-Reply-To: <1392737687-25003-2-git-send-email-p.zabel@pengutronix.de>
On Tuesday 18 February 2014 16:34:41 Philipp Zabel wrote:
> +
> +Example of a device that is part of a power domain:
> +
> + vpu: vpu at 02040000 {
> + reg = <0x02040000 0x3c000>;
> + /* ... */
> + fsl,power-domain = <&pd_pu>;
> + /* ... */
> + };
> +
I'm really not too happy about platforms starting to add random
bindings for power domains. Unfortunately I didn't catch exynos
doing this first, but I don't want to see another platform like
that.
Can we please come up with a proper generic power domain binding
first and then add platform specific users?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v4 1/7] Documentation: Add device tree bindings for Freescale i.MX GPC
Date: Tue, 18 Feb 2014 19:10:03 +0100 [thread overview]
Message-ID: <2328803.HhaG6blXIR@wuerfel> (raw)
In-Reply-To: <1392737687-25003-2-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Tuesday 18 February 2014 16:34:41 Philipp Zabel wrote:
> +
> +Example of a device that is part of a power domain:
> +
> + vpu: vpu@02040000 {
> + reg = <0x02040000 0x3c000>;
> + /* ... */
> + fsl,power-domain = <&pd_pu>;
> + /* ... */
> + };
> +
I'm really not too happy about platforms starting to add random
bindings for power domains. Unfortunately I didn't catch exynos
doing this first, but I don't want to see another platform like
that.
Can we please come up with a proper generic power domain binding
first and then add platform specific users?
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-18 18:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 15:34 [PATCH v4 0/7] i.MX6 PU power domain support Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 1/7] Documentation: Add device tree bindings for Freescale i.MX GPC Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 18:10 ` Arnd Bergmann [this message]
2014-02-18 18:10 ` Arnd Bergmann
2014-02-19 9:30 ` Philipp Zabel
2014-02-19 9:30 ` Philipp Zabel
2014-02-19 14:38 ` Arnd Bergmann
2014-02-19 14:38 ` Arnd Bergmann
2014-02-19 14:51 ` Tomasz Figa
2014-02-19 14:51 ` Tomasz Figa
2014-02-19 14:56 ` Arnd Bergmann
2014-02-19 14:56 ` Arnd Bergmann
2014-02-19 16:00 ` Philipp Zabel
2014-02-19 16:00 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 2/7] ARM: imx6: gpc: Add PU power domain for GPU/VPU Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 3/7] ARM: imx6: gpc: Add pm clock support to PU power domain Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 4/7] ARM: imx6: gpc: Add observed worst case latencies Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 5/7] ARM: dts: imx6qdl: Allow disabling the PU regulator, add a enable ramp delay Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 6/7] ARM: dts: imx6qdl: Add power-domain information to gpc node Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
2014-02-18 15:34 ` [PATCH v4 7/7] ARM: dts: imx6sl: " Philipp Zabel
2014-02-18 15:34 ` Philipp Zabel
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=2328803.HhaG6blXIR@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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.