From: Marek Vasut <marex@denx.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
Mans Rullgard <mans@mansr.com>,
Olaf Mandel <o.mandel@menlosystems.com>,
Semen Protsenko <semen.protsenko@globallogic.com>
Subject: Re: [PATCH] gpio: max732x: Add missing dev reference to gpiochip
Date: Fri, 14 Aug 2015 23:10:58 +0200 [thread overview]
Message-ID: <201508142310.58606.marex@denx.de> (raw)
In-Reply-To: <CACRpkdZ_MWwfjExjvW59+dQ=E2rv4c9_MsSsjNwO5M8yM+j9fg@mail.gmail.com>
On Thursday, July 16, 2015 at 01:43:13 PM, Linus Walleij wrote:
> On Tue, Jun 30, 2015 at 8:04 PM, Marek Vasut <marex@denx.de> wrote:
> > In case the gpiochip doesn't have the .dev field set, as is the case
> > in here, it is not possible to reference this device in DT as a GPIO
> > controller. A good example of this problem is that gpio-leds can not
> > be used when connected to this chip, the gpio-leds driver bails out
> > with -EPROBE_DEFER.
> >
> > Fix this problem by setting the .dev field of the gpio_chip to the
> > parent i2c device.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Alexandre Courbot <gnurou@gmail.com>
> > Cc: Linus Walleij <linus.walleij@linaro.org>
> > Cc: Mans Rullgard <mans@mansr.com>
> > Cc: Olaf Mandel <o.mandel@menlosystems.com>
> > Cc: Semen Protsenko <semen.protsenko@globallogic.com>
>
> Patch applied for fixes.
Hi,
I don't see this one in -next , did it get lost or something please ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-08-14 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 18:04 [PATCH] gpio: max732x: Add missing dev reference to gpiochip Marek Vasut
2015-07-16 11:43 ` Linus Walleij
2015-08-14 21:10 ` Marek Vasut [this message]
2015-08-20 8:23 ` Linus Walleij
2015-08-20 9:03 ` Marek Vasut
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=201508142310.58606.marex@denx.de \
--to=marex@denx.de \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mans@mansr.com \
--cc=o.mandel@menlosystems.com \
--cc=semen.protsenko@globallogic.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;
as well as URLs for NNTP newsgroup(s).