From: Hans de Goede <hdegoede@redhat.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC v2 1/2] dt-bindings: simplefb: Support a list of regulator supply properties
Date: Wed, 21 Oct 2015 07:50:49 +0000 [thread overview]
Message-ID: <562743D9.4030809@redhat.com> (raw)
In-Reply-To: <1445407141-16459-2-git-send-email-wens@csie.org>
Hi,
On 21-10-15 07:59, Chen-Yu Tsai wrote:
> The physical display tied to the framebuffer may have regulators
> providing power to it, such as power for LCDs or interface conversion
> chips.
>
> The number of regulators in use may vary, but the regulator supply
> binding can not be a list. Work around this by adding a "num-supplies"
> property to communicate the number of supplies, and a list of 0 ~ N
> "vinN-supply" properties for the actual regulator supply.
This bit of the commit message is no longer accurate. Other then that
this patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> ---
> .../devicetree/bindings/video/simple-framebuffer.txt | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/video/simple-framebuffer.txt b/Documentation/devicetree/bindings/video/simple-framebuffer.txt
> index 4474ef6e0b95..8c9e9f515c87 100644
> --- a/Documentation/devicetree/bindings/video/simple-framebuffer.txt
> +++ b/Documentation/devicetree/bindings/video/simple-framebuffer.txt
> @@ -47,10 +47,14 @@ Required properties:
> - a8b8g8r8 (32-bit pixels, d[31:24]=a, d[23:16]=b, d[15:8]=g, d[7:0]=r).
>
> Optional properties:
> -- clocks : List of clocks used by the framebuffer. Clocks listed here
> - are expected to already be configured correctly. The OS must
> - ensure these clocks are not modified or disabled while the
> - simple framebuffer remains active.
> +- clocks : List of clocks used by the framebuffer.
> +- *-supply : Any number of regulators used by the framebuffer. These should
> + be named according to the names in the device's design.
> +
> + The above resources are expected to already be configured correctly.
> + The OS must ensure they are not modified or disabled while the simple
> + framebuffer remains active.
> +
> - display : phandle pointing to the primary display hardware node
>
> Example:
> @@ -68,6 +72,7 @@ chosen {
> stride = <(1600 * 2)>;
> format = "r5g6b5";
> clocks = <&ahb_gates 36>, <&ahb_gates 43>, <&ahb_gates 44>;
> + lcd-supply = <®_dc1sw>;
> display = <&lcdc0>;
> };
> stdout-path = "display0";
>
next prev parent reply other threads:[~2015-10-21 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 5:58 [PATCH RFC v2 0/2] simplefb: Add regulator handling support Chen-Yu Tsai
2015-10-21 5:59 ` [PATCH RFC v2 1/2] dt-bindings: simplefb: Support a list of regulator supply properties Chen-Yu Tsai
2015-10-21 7:50 ` Hans de Goede [this message]
2015-10-21 5:59 ` [PATCH RFC v2 2/2] simplefb: Claim and enable regulators Chen-Yu Tsai
2015-10-21 7:54 ` Hans de Goede
2015-10-21 8:04 ` Chen-Yu Tsai
2015-10-21 8:09 ` Hans de Goede
2015-10-22 16:53 ` [PATCH RFC v2 0/2] simplefb: Add regulator handling support Mark Brown
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=562743D9.4030809@redhat.com \
--to=hdegoede@redhat.com \
--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 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).