From: Tony Lindgren <tony@atomide.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-omap <linux-omap@vger.kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [PATCH] mmc: pwrseq_simple: Fix regression with optional GPIOs
Date: Fri, 18 Dec 2015 08:14:06 -0800 [thread overview]
Message-ID: <20151218161406.GL23396@atomide.com> (raw)
In-Reply-To: <CAPDyKFpxiOJJdh-nLXjxv3DYJnW3RAf_9aqMfds46=-oqPd5ng@mail.gmail.com>
* Ulf Hansson <ulf.hansson@linaro.org> [151207 16:20]:
> +Linus
>
> On 7 December 2015 at 23:54, Tony Lindgren <tony@atomide.com> wrote:
> > Commit ce037275861e ("mmc: pwrseq_simple: use GPIO descriptors array API")
> > changed the handling MMC power sequence so GPIOs no longer are optional.
> >
> > This broke SDIO WLAN at least for omap5 that can't yet use the reset GPIOs
> > with pwrseq_simple as a wait is needed after enabling the SDIO device.
>
> Can you elaborate on this. Did it break omap5 or not? :-)
Ulf, is this patch queued for v4.4 as a regression fix? I don't see it
in Linux next or mainline trees?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: pwrseq_simple: Fix regression with optional GPIOs
Date: Fri, 18 Dec 2015 08:14:06 -0800 [thread overview]
Message-ID: <20151218161406.GL23396@atomide.com> (raw)
In-Reply-To: <CAPDyKFpxiOJJdh-nLXjxv3DYJnW3RAf_9aqMfds46=-oqPd5ng@mail.gmail.com>
* Ulf Hansson <ulf.hansson@linaro.org> [151207 16:20]:
> +Linus
>
> On 7 December 2015 at 23:54, Tony Lindgren <tony@atomide.com> wrote:
> > Commit ce037275861e ("mmc: pwrseq_simple: use GPIO descriptors array API")
> > changed the handling MMC power sequence so GPIOs no longer are optional.
> >
> > This broke SDIO WLAN at least for omap5 that can't yet use the reset GPIOs
> > with pwrseq_simple as a wait is needed after enabling the SDIO device.
>
> Can you elaborate on this. Did it break omap5 or not? :-)
Ulf, is this patch queued for v4.4 as a regression fix? I don't see it
in Linux next or mainline trees?
Regards,
Tony
next prev parent reply other threads:[~2015-12-18 16:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 22:54 [PATCH] mmc: pwrseq_simple: Fix regression with optional GPIOs Tony Lindgren
2015-12-07 22:54 ` Tony Lindgren
2015-12-08 0:19 ` Ulf Hansson
2015-12-08 0:19 ` Ulf Hansson
2015-12-08 0:32 ` Tony Lindgren
2015-12-08 0:32 ` Tony Lindgren
2015-12-08 1:53 ` Javier Martinez Canillas
2015-12-08 1:53 ` Javier Martinez Canillas
2015-12-08 13:17 ` Ulf Hansson
2015-12-08 13:17 ` Ulf Hansson
2015-12-08 15:57 ` Tony Lindgren
2015-12-08 15:57 ` Tony Lindgren
2015-12-18 16:14 ` Tony Lindgren [this message]
2015-12-18 16:14 ` Tony Lindgren
2015-12-18 22:19 ` Ulf Hansson
2015-12-18 22:19 ` Ulf Hansson
2015-12-18 22:31 ` Tony Lindgren
2015-12-18 22:31 ` Tony Lindgren
2015-12-28 12:18 ` Ulf Hansson
2015-12-28 12:18 ` Ulf Hansson
2015-12-28 21:28 ` Tony Lindgren
2015-12-28 21:28 ` Tony Lindgren
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=20151218161406.GL23396@atomide.com \
--to=tony@atomide.com \
--cc=javier@osg.samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.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.