public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Dietrich <marvin24@gmx.de>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Alexandre Courbot <gnurou@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: tegra: paz00: use con_id's to refer GPIO's ingpiod_lookup table
Date: Tue, 08 Sep 2015 09:59:11 +0200	[thread overview]
Message-ID: <3738507.JjVW9EvTJ3@fb07-iapwap2> (raw)
In-Reply-To: <55ED5721.80508@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

Am Montag, 7. September 2015, 12:21:37 schrieb Dmitry Osipenko:
> 30.06.2015 17:15, Dmitry Osipenko пишет:
> > Commit 72daceb9a10a ("net: rfkill: gpio: Add default GPIO driver mappings
> > for ACPI") removed possibility to request GPIO by table index for non-ACPI
> > platforms without changing it users. As result "shutdown" GPIO request
> > will fail if request for "reset" GPIO succeeded or "reset" will be
> > requested instead of "shutdown" if "reset" wasn't defined. Fix it by
> > making gpiod_lookup_table use con_id's instead of indexes.
> > 
> > Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> > Fixes: 72daceb (net: rfkill: gpio: Add default GPIO driver mappings for
> > ACPI) Cc: <stable@vger.kernel.org> # v3.19+
> > Acked-by: Alexandre Courbot <acourbot@nvidia.com>
> > ---
> > 
> > v2: s/GPIO_LOOKUP_IDX/GPIO_LOOKUP/, otherwise "shutdown" GPIO won't be
> > requested> 
> >   arch/arm/mach-tegra/board-paz00.c | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/mach-tegra/board-paz00.c
> > b/arch/arm/mach-tegra/board-paz00.c index fbe74c6..49d1110 100644
> > --- a/arch/arm/mach-tegra/board-paz00.c
> > +++ b/arch/arm/mach-tegra/board-paz00.c
> > @@ -39,8 +39,8 @@ static struct platform_device wifi_rfkill_device = {
> > 
> >   static struct gpiod_lookup_table wifi_gpio_lookup = {
> >   
> >   	.dev_id = "rfkill_gpio",
> >   	.table = {
> > 
> > -		GPIO_LOOKUP_IDX("tegra-gpio", 25, NULL, 0, 0),
> > -		GPIO_LOOKUP_IDX("tegra-gpio", 85, NULL, 1, 0),
> > +		GPIO_LOOKUP("tegra-gpio", 25, "reset", 0),
> > +		GPIO_LOOKUP("tegra-gpio", 85, "shutdown", 0),
> > 
> >   		{ },
> >   	
> >   	},
> >   
> >   };
> 
> Ping

also 

Tested-by: Marc Dietrich <marvin24@gmx.de>

I thing this should go through the tegra-soc tree. Thierry? Stephen?

Marc

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-09-08  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 14:15 [PATCH v2] ARM: tegra: paz00: use con_id's to refer GPIO's in gpiod_lookup table Dmitry Osipenko
2015-06-30 20:44 ` Marc Dietrich
2015-09-07  9:21 ` Dmitry Osipenko
2015-09-08  7:59   ` Marc Dietrich [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=3738507.JjVW9EvTJ3@fb07-iapwap2 \
    --to=marvin24@gmx.de \
    --cc=digetx@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    /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