From: Hans de Goede <hdegoede@redhat.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] simplefb: Add regulator handling support
Date: Fri, 23 Oct 2015 13:49:31 +0000 [thread overview]
Message-ID: <562A3AEB.2080502@redhat.com> (raw)
In-Reply-To: <1445572241-13259-1-git-send-email-wens@csie.org>
Hi,
Patches 1/2 look good and are:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
And the approach used for the regulators in them is also:
Acked-by: Mark Brown <broonie@kernel.org>
So patches 1/2 are ready for merging.
Jean-Christophe or Tomi, can you pick up patch 1 & 2 please ?
Regards,
Hans
On 10/23/2015 05:50 AM, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This is v4 of the simplefb regulator support series. This series adds
> regulator claiming and enabling support for simplefb.
>
> Changes since v4:
> - Fixed inverted logic when testing the property name.
> - Fixed regulator supply name string copy length off by 1.
> - Added real world user, MSI Primo 81 dts patches.
>
> Changes since v3:
> - Dropped extra "if" which is always true, leftover from v1.
> - Updated commit message of patch 1
>
> Sometimes the simplefb display output path consits of external conversion
> chips and/or LCD drivers and backlights. These devices normally have
> GPIOs to turn them on and/or bring them out of reset, and regulators
> supplying power to them.
>
> While the kernel does not touch unclaimed GPIOs, the regulator core
> happily disables unused regulators. Thus we need simplefb to claim
> and enable the regulators used throughout the display pipeline.
>
> The binding supports any named regulator supplies under its device
> node. The driver will look through its properties, and claim any
> regulators by matching "*-supply", as Mark suggested.
>
> I've not done a generic helper in the regulator core yet, instead doing
> the regulator property handling in the simplefb code for now.
>
>
> Patch 1 adds the regulator properties to the DT binding.
>
> Patch 2 adds code to the simplefb driver to claim and enable regulators.
> Hans, I dropped your Reviewed-by tag from this patch.
>
> Patch 3 adds labels to the simplefb device nodes in sun6i-a31.dtsi
> so we can reference them in the board dts files, like in the next
> patch.
>
> Patch 4 adds a dts file for MSI's Primo 81 tablet.
>
>
> Regards
> ChenYu
>
> Chen-Yu Tsai (3):
> dt-bindings: simplefb: Support regulator supply properties
> simplefb: Claim and enable regulators
> ARM: dts: sun6i: Add simplefb node labels to reference at board level
>
> Karsten Merker (1):
> ARM: dts: sun6i: Add dts file for MSI Primo81 tablet
>
> .../bindings/video/simple-framebuffer.txt | 13 +-
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/sun6i-a31.dtsi | 4 +-
> arch/arm/boot/dts/sun6i-a31s-primo81.dts | 255 +++++++++++++++++++++
> drivers/video/fbdev/simplefb.c | 120 +++++++++-
> 5 files changed, 386 insertions(+), 7 deletions(-)
> create mode 100644 arch/arm/boot/dts/sun6i-a31s-primo81.dts
>
prev parent reply other threads:[~2015-10-23 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 3:50 [PATCH v4 0/4] simplefb: Add regulator handling support Chen-Yu Tsai
2015-10-23 3:50 ` [PATCH v4 1/4] dt-bindings: simplefb: Support regulator supply properties Chen-Yu Tsai
2015-10-23 3:50 ` [PATCH v4 2/4] simplefb: Claim and enable regulators Chen-Yu Tsai
2015-10-23 3:50 ` [PATCH v4 3/4] ARM: dts: sun6i: Add simplefb node labels to reference at board level Chen-Yu Tsai
2015-10-23 3:50 ` [PATCH v4 4/4] ARM: dts: sun6i: Add dts file for MSI Primo81 tablet Chen-Yu Tsai
[not found] ` <20151023145309.GA1885@excalibur.cnev.de>
2015-10-23 15:46 ` Chen-Yu Tsai
2015-10-23 15:56 ` Chen-Yu Tsai
[not found] ` <20151023165641.GB1885@excalibur.cnev.de>
2015-10-24 3:15 ` Chen-Yu Tsai
2015-10-24 7:09 ` Maxime Ripard
2015-10-24 9:33 ` Siarhei Siamashka
2015-10-23 6:05 ` [PATCH v4 0/4] simplefb: Add regulator handling support Maxime Ripard
2015-10-23 13:49 ` Hans de Goede [this message]
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=562A3AEB.2080502@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).