From: Kevin Hilman <khilman@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Olof Johansson <olof@lixom.net>,
Simon Horman <horms+renesas@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-sh@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3/resend 3/4] drivers: bus: Add Simple Power-Managed Bus DT Bindings
Date: Thu, 22 Jan 2015 14:42:08 -0800 [thread overview]
Message-ID: <7hvbjy30an.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1421919253-4784-4-git-send-email-geert+renesas@glider.be> (Geert Uytterhoeven's message of "Thu, 22 Jan 2015 10:34:12 +0100")
Geert Uytterhoeven <geert+renesas@glider.be> writes:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Tested-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> ---
> v3:
> - Add Tested-by,
> - Document required properties inherited from "simple-bus",
> - Document required "reg" property for "renesas,bsc",
> - Move "ranges" before "reg" in the example,
>
> v2:
> - New.
> ---
> .../devicetree/bindings/bus/simple-pm-bus.txt | 52 ++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/simple-pm-bus.txt
>
> diff --git a/Documentation/devicetree/bindings/bus/simple-pm-bus.txt b/Documentation/devicetree/bindings/bus/simple-pm-bus.txt
> new file mode 100644
> index 0000000000000000..d03abf7fd8e3997a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/simple-pm-bus.txt
> @@ -0,0 +1,52 @@
> +Simple Power-Managed Bus
> +========================
> +
> +A Simple Power-Managed Bus is a transparent bus that doesn't need a real
> +driver, as it's typically initialized by the boot loader.
> +
> +However, its bus controller is part of a PM domain, or under the control of a
> +functional clock. Hence, the bus controller's PM domain and/or clock must be
> +enabled for child devices connected to the bus (either on-SoC or externally)
> +to function.
> +
> +
> +Generic compatible values and properties
> +----------------------------------------
> +
> +Required properties:
> + - compatible: Must be at least one of the vendor-specific compatible values
> + from a vendor-specific section below, and "simple-bus" as a
> + fallback.
What happened to the idea of using something like "simple-pm-bus"?
There's nothing vendor-specific in the driver at all, so the
vendor-specific binding seem like clutter to me and will result in
continuing to add vendor-specific compatibles without any
vendor-specific code.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3/resend 3/4] drivers: bus: Add Simple Power-Managed Bus DT Bindings
Date: Thu, 22 Jan 2015 22:42:08 +0000 [thread overview]
Message-ID: <7hvbjy30an.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1421919253-4784-4-git-send-email-geert+renesas@glider.be> (Geert Uytterhoeven's message of "Thu, 22 Jan 2015 10:34:12 +0100")
Geert Uytterhoeven <geert+renesas@glider.be> writes:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Tested-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> ---
> v3:
> - Add Tested-by,
> - Document required properties inherited from "simple-bus",
> - Document required "reg" property for "renesas,bsc",
> - Move "ranges" before "reg" in the example,
>
> v2:
> - New.
> ---
> .../devicetree/bindings/bus/simple-pm-bus.txt | 52 ++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/simple-pm-bus.txt
>
> diff --git a/Documentation/devicetree/bindings/bus/simple-pm-bus.txt b/Documentation/devicetree/bindings/bus/simple-pm-bus.txt
> new file mode 100644
> index 0000000000000000..d03abf7fd8e3997a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/simple-pm-bus.txt
> @@ -0,0 +1,52 @@
> +Simple Power-Managed Bus
> +============
> +
> +A Simple Power-Managed Bus is a transparent bus that doesn't need a real
> +driver, as it's typically initialized by the boot loader.
> +
> +However, its bus controller is part of a PM domain, or under the control of a
> +functional clock. Hence, the bus controller's PM domain and/or clock must be
> +enabled for child devices connected to the bus (either on-SoC or externally)
> +to function.
> +
> +
> +Generic compatible values and properties
> +----------------------------------------
> +
> +Required properties:
> + - compatible: Must be at least one of the vendor-specific compatible values
> + from a vendor-specific section below, and "simple-bus" as a
> + fallback.
What happened to the idea of using something like "simple-pm-bus"?
There's nothing vendor-specific in the driver at all, so the
vendor-specific binding seem like clutter to me and will result in
continuing to add vendor-specific compatibles without any
vendor-specific code.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3/resend 3/4] drivers: bus: Add Simple Power-Managed Bus DT Bindings
Date: Thu, 22 Jan 2015 14:42:08 -0800 [thread overview]
Message-ID: <7hvbjy30an.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1421919253-4784-4-git-send-email-geert+renesas@glider.be> (Geert Uytterhoeven's message of "Thu, 22 Jan 2015 10:34:12 +0100")
Geert Uytterhoeven <geert+renesas@glider.be> writes:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Tested-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> ---
> v3:
> - Add Tested-by,
> - Document required properties inherited from "simple-bus",
> - Document required "reg" property for "renesas,bsc",
> - Move "ranges" before "reg" in the example,
>
> v2:
> - New.
> ---
> .../devicetree/bindings/bus/simple-pm-bus.txt | 52 ++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/simple-pm-bus.txt
>
> diff --git a/Documentation/devicetree/bindings/bus/simple-pm-bus.txt b/Documentation/devicetree/bindings/bus/simple-pm-bus.txt
> new file mode 100644
> index 0000000000000000..d03abf7fd8e3997a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/simple-pm-bus.txt
> @@ -0,0 +1,52 @@
> +Simple Power-Managed Bus
> +========================
> +
> +A Simple Power-Managed Bus is a transparent bus that doesn't need a real
> +driver, as it's typically initialized by the boot loader.
> +
> +However, its bus controller is part of a PM domain, or under the control of a
> +functional clock. Hence, the bus controller's PM domain and/or clock must be
> +enabled for child devices connected to the bus (either on-SoC or externally)
> +to function.
> +
> +
> +Generic compatible values and properties
> +----------------------------------------
> +
> +Required properties:
> + - compatible: Must be at least one of the vendor-specific compatible values
> + from a vendor-specific section below, and "simple-bus" as a
> + fallback.
What happened to the idea of using something like "simple-pm-bus"?
There's nothing vendor-specific in the driver at all, so the
vendor-specific binding seem like clutter to me and will result in
continuing to add vendor-specific compatibles without any
vendor-specific code.
Kevin
next prev parent reply other threads:[~2015-01-22 22:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 9:34 [PATCH v3/resend 0/4] drivers: bus: Add Simple Power-Managed Bus Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` [PATCH v3/resend 1/4] drivers: bus: Sort Kconfig entries alphabetically Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` [PATCH v3/resend 2/4] drivers: bus: Sort Makefile " Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` [PATCH v3/resend 3/4] drivers: bus: Add Simple Power-Managed Bus DT Bindings Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 22:42 ` Kevin Hilman [this message]
2015-01-22 22:42 ` Kevin Hilman
2015-01-22 22:42 ` Kevin Hilman
[not found] ` <7hvbjy30an.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2015-01-23 8:56 ` Geert Uytterhoeven
2015-01-23 8:56 ` Geert Uytterhoeven
2015-01-23 8:56 ` Geert Uytterhoeven
2015-01-23 8:56 ` Geert Uytterhoeven
2015-01-23 13:46 ` Arnd Bergmann
2015-01-23 13:46 ` Arnd Bergmann
2015-01-23 13:46 ` Arnd Bergmann
2015-01-23 14:18 ` Geert Uytterhoeven
2015-01-23 14:18 ` Geert Uytterhoeven
2015-01-23 14:18 ` Geert Uytterhoeven
2015-01-23 14:34 ` Mark Rutland
2015-01-23 14:34 ` Mark Rutland
2015-01-23 14:34 ` Mark Rutland
2015-01-22 9:34 ` [PATCH v3/resend 4/4] drivers: bus: Add Simple Power-Managed Bus Driver Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
2015-01-22 9:34 ` Geert Uytterhoeven
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=7hvbjy30an.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@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.