All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stefan Agner <stefan@agner.ch>
Cc: stable@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
	stable@kernel.org
Subject: Re: [PATCH] i2c: imx: defer probe if bus recovery GPIOs are not ready
Date: Wed, 9 Nov 2016 07:11:45 +0100	[thread overview]
Message-ID: <20161109061145.GB2739@kroah.com> (raw)
In-Reply-To: <847750bba7bed752906f75f5df3f8344@agner.ch>

On Tue, Nov 08, 2016 at 04:34:50PM -0800, Stefan Agner wrote:
> On 2016-11-08 16:32, Stefan Agner wrote:
> > commit 533169d164c6b4c8571d0d48779f6ff6be593d72 upstream.
> > 
> > Some SoC might load the GPIO driver after the I2C driver and
> > using the I2C bus recovery mechanism via GPIOs. In this case
> > it is crucial to defer probing if the GPIO request functions
> > do so, otherwise the I2C driver gets loaded without recovery
> > mechanisms enabled.
> > 
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
> > Acked-by: Uwe Kleine-K�nig <u.kleine-koenig@pengutronix.de>
> > Acked-by: Li Yang <leoyang.li@nxp.com>
> > Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> > Cc: stable@kernel.org
> 
> I forgot to mention, this should be applied to 4.4 only.

Did you build the code there?

> Later versions made the return value void, and it would require a larger
> rework. I am mainly concerned about LTS...

I don't see this working for either 4.4 or 4.8-stable right now, do you?

confused,

greg k-h

  reply	other threads:[~2016-11-09  6:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  0:32 [PATCH] i2c: imx: defer probe if bus recovery GPIOs are not ready Stefan Agner
2016-11-09  0:34 ` Stefan Agner
2016-11-09  6:11   ` Greg KH [this message]
2016-11-09 18:45     ` Stefan Agner
2016-11-09  6:10 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2016-09-27  0:18 Stefan Agner
2016-09-27  6:44 ` Uwe Kleine-König
2016-09-27 18:31 ` Leo Li
2016-10-25 10:16 ` Wolfram Sang

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=20161109061145.GB2739@kroah.com \
    --to=greg@kroah.com \
    --cc=stable@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stefan@agner.ch \
    --cc=wsa@the-dreams.de \
    /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.