linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/37] ARM: dts: Fix fixed regulators enable GPIO polarity
Date: Mon, 12 Oct 2015 15:24:25 -0700	[thread overview]
Message-ID: <20151012222424.GJ23801@atomide.com> (raw)
In-Reply-To: <5696453.QxruGxICMQ@avalon>

* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [151012 15:26]:
> Hi Javier,
> 
> On Tuesday 13 October 2015 00:19:20 Javier Martinez Canillas wrote:
> > On 10/12/2015 11:46 PM, Tony Lindgren wrote:
> > > * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [151012 14:17]:
> > >> Hello,
> > >> 
> > >> While working on regulators, GPIOs and DT I noticed that many of our DT
> > >> source files incorrectly describe fixed regulators. The common error
> > >> patterns are
> > >> 
> > >> - Usage of the undefined (and never parsed) enable-active-low property
> > >> - Usage of the enable-active-high property without specifying an enable
> > >>   GPIO
> > >> - Typos in the enabl GPIO property name (gpios instead of gpio)
> > >> - Mismatch between the enable-active-high property (or the lack thereof)
> > >>   and the enable GPIO flags
> > >> 
> > >> This patch series fixes those issues in all the DT sources after locating
> > >> the errors using the following script.
> > >> 
> > >> -------------------------------------------------------------------------
> > >> !/bin/sh
> > >> 
> > >> echo $1
> > >> cat $1 | awk '
> > >> BEGIN {
> > >> 	open_drain = 0;
> > >> 	active_high = 0;
> > >> 	gpio = 0;
> > >> 	flags = 0;
> > >> }
> > >> 
> > >> match($0, /([a-zA-Z0-9 at _-]*) {/, ary) {
> > >> 	name = ary[1];
> > >> }
> > >> 
> > >> /compatible.*"regulator-fixed"/ {
> > >> 	found = 1;
> > >> }
> > >> 
> > >> /enable-active-high/ {
> > >> 	active_high = 1;
> > >> }
> > >> 
> > >> /gpio-open-drain/ {
> > >> 	open_drain = 1;
> > >> }
> > >> 
> > >> match($0, /gpio += <.* ([^ ]*)>/, ary) {
> > >> 	gpio = 1;
> > >> 	flags = ary[1];
> > >> 	if (flags == 0)
> > >> 		flags = "GPIO_ACTIVE_HIGH";
> > >> }
> > >> 
> > >> /}/ {
> > >> 	if (found) {
> > >> 		if (gpio) {
> > >> 			print "\t" name ": active high " active_high " " flags " open 
> drain "
> > >> 			open_drain;
> > >> 			if ((active_high && flags == "GPIO_ACTIVE_LOW") ||
> > >> 			    (!active_high && flags == "GPIO_ACTIVE_HIGH"))
> > >> 				print "WARNING: enable-active-high and flags do not 
> match"
> > >> 		} else {
> > >> 			if (active_high)
> > >> 				print "WARNING: active high without GPIO"
> > >> 			if (open_drain)
> > >> 				print "WARNING: open drain without GPIO"
> > >> 		}
> > >> 	}
> > >> 	
> > >> 	gpio = 0;
> > >> 	found = 0;
> > >> 	active_high = 0;
> > >> 	open_drain = 0;
> > >> 	flags = 0;
> > >> }
> > >> '
> > >> -------------------------------------------------------------------------
> > >> 
> > >> All patches except for the ones touching omap3-beagle-xm and
> > >> omap3-overo-base are untested as I lack test hardware.
> > >> 
> > >> As there's no dependency between the patches touching different source
> > >> files the appropriate maintainers could take their share of the patches
> > >> in their tree. Alternatively I could send a single pull request after
> > >> collecting all acks but that might be more complex.
> > > 
> > > Nice clean-up. For omaps, there's an earlier patch posted by
> > > Javier Martinez Canillas <javier@osg.samsung.com> as "[PATCH] ARM: dts:
> > > Use defined GPIO constants in flags cell for OMAP2+ boards". Can you guys
> > > do some cross checking and let me know which combination I should appluy
> > > for omaps?
> >
> > Since Laurent's changes for OMAP are part of a bigger series and my patch
> > was only for OMAP, probably makes sense for you to pick his patches and I
> > can re-spin mine on top of that.
> > 
> > BTW, I posted as a single patch since the changes were trivial but maybe
> > that made handling these conflicts harder and I should split the changes
> > instead, since I'll resend anyways.
> > 
> > What do you prefer? a patch per SoC family (i.e: OMAP{2,3,4,5}) or patch
> > per board DTS?
> 
> My series will likely miss the next merge window as more discussion is needed. 
> I'll thus respin the patches on top of yours, please proceed without caring 
> about this.

OK applying Javier's patch into omap-for-v4.4/dt then.

Regards,

Tony

  reply	other threads:[~2015-10-12 22:24 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 21:12 [PATCH 00/37] ARM: dts: Fix fixed regulators enable GPIO polarity Laurent Pinchart
2015-10-12 21:12 ` [PATCH 01/37] ARM: dts: am437x-gp-evm: Remove unneeded regulator property Laurent Pinchart
2015-10-12 21:12 ` [PATCH 02/37] ARM: dts: am43xx-epos-evm: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 03/37] ARM: mvebu: Armada 388 GP: " Laurent Pinchart
2015-10-13  8:37   ` Thomas Petazzoni
2015-10-12 21:12 ` [PATCH 04/37] ARM: imx6sx-sdb: Fix typo in regulator enable GPIO property Laurent Pinchart
2015-10-12 21:12 ` [PATCH 05/37] ARM: dts: s5pv210-aquila: " Laurent Pinchart
2015-10-13  0:20   ` Krzysztof Kozlowski
2015-10-12 21:12 ` [PATCH 06/37] ARM: dts: s5pv210-goni: " Laurent Pinchart
2015-10-13  0:20   ` Krzysztof Kozlowski
2015-10-12 21:12 ` [PATCH 07/37] ARM: dts: omap3-evm: Remove invalid enable-active-low regulator property Laurent Pinchart
2015-10-12 21:12 ` [PATCH 08/37] ARM: dts: omap3-sb-t35: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 09/37] ARM: dts: omap3-tao3530: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 10/37] ARM: dts: imx6qdl-tx6: Fix regulator enable GPIO polarity Laurent Pinchart
2015-10-12 21:12 ` [PATCH 11/37] ARM: dts: dove-cm-a510: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 12/37] ARM: dts: dove-sbc-a510: " Laurent Pinchart
2015-10-12 22:50   ` Jason Cooper
2015-10-12 23:10     ` Laurent Pinchart
2015-10-12 23:26       ` Jason Cooper
2015-10-12 21:12 ` [PATCH 13/37] ARM: dts: exynos5250-arndale: " Laurent Pinchart
2015-10-13 14:11   ` Shawn Guo
2015-10-12 21:12 ` [PATCH 14/37] ARM: dts: imx23-evk: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 15/37] ARM: dts: imx23-stmp378x_devb: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 16/37] ARM: dts: imx25-pdk: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 17/37] ARM: dts: imx28-cfa10036: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 18/37] ARM: dts: imx28-evk: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 19/37] ARM: dts: imx28-m28cu3: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 20/37] ARM: dts: imx28-m28evk: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 21/37] ARM: dts: imx28-sps1: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 22/37] ARM: dts: imx28-tx28: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 23/37] ARM: dts: imx53-m53evk: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 24/37] ARM: dts: imx53-mba53: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 25/37] ARM: dts: imx53-tx53: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 26/37] ARM: dts: imx6q-dmo-edmqmx6: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 27/37] ARM: dts: kirkwood-blackarmor-nas220: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 28/37] ARM: dts: omap4-duovero: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 29/37] ARM: dts: kirkwood-nsa3x0-common: " Laurent Pinchart
2015-10-12 21:12 ` [PATCH 30/37] ARM: dts: omap3-beagle-xm: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 31/37] ARM: dts: omap3-beagle: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 32/37] ARM: dts: omap3-overo-base: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 33/37] ARM: dts: omap3-tao3530: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 34/37] ARM: dts: tegra20-harmony: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 35/37] ARM: dts: tegra20-iris-512: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 36/37] ARM: dts: tegra20-seaboard: " Laurent Pinchart
2015-10-12 21:13 ` [PATCH 37/37] ARM: dts: tegra20-ventana: " Laurent Pinchart
2015-10-12 21:34   ` Stephen Warren
2015-10-12 22:24     ` Laurent Pinchart
2015-10-13 16:35       ` Stephen Warren
2015-10-12 21:46 ` [PATCH 00/37] ARM: dts: Fix fixed regulators " Tony Lindgren
2015-10-12 22:19   ` Javier Martinez Canillas
2015-10-12 22:22     ` Laurent Pinchart
2015-10-12 22:24       ` Tony Lindgren [this message]
2015-10-13  6:19 ` Sascha Hauer
2015-10-13 14:09 ` Shawn Guo
2015-10-13 14:17   ` Laurent Pinchart
2015-10-13 15:09     ` Shawn Guo

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=20151012222424.GJ23801@atomide.com \
    --to=tony@atomide.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).