All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v1] pinctrl: intel: Actually disable Tx and Rx buffers on GPIO request
Date: Tue, 8 Dec 2020 11:48:53 +0200	[thread overview]
Message-ID: <20201208094853.GF4077@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdb4AYx1dOYkZvHzRD7fbGfVbKoGqdnmh1m=rdhGnAaPag@mail.gmail.com>

On Tue, Dec 08, 2020 at 09:34:43AM +0100, Linus Walleij wrote:
> On Mon, Dec 7, 2020 at 7:07 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Mon, Dec 7, 2020 at 8:02 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > Mistakenly the buffers (input and output) become together enabled for a little
> > > period of time during GPIO request. This is problematic, because instead of
> > > initial motive to disable them in the commit af7e3eeb84e2
> > > ("pinctrl: intel: Disable input and output buffer when switching to GPIO"),
> > > the driven value on the pin, which might be used as an IRQ line, brings
> > > firmware of some touch pads in an awkward state that needs a full power off
> > > to recover. Fix this by, as stated in a culprit commit, disabling the buffers.
> >
> > Linus, since we are at rc7 I'm not going to send a PR for this single
> > fix (I truly do not expect anything to come). Please, proceed as usual
> > (either to v5.10 or to v5.11 cycle, there is not much difference b/c
> > culptin is sitting in v5.9).
> 
> OK no problem, I applied the patch directly for fixes so we get it in ASAP.

Linus, thanks, however something happened to it. i.e. BugLink tag disappeared.
It's not good, because due to that link and Kai's report I quickly understood
what was the issue.

Besides that commit message has some grammar / style issues.
Can you please fix above and use below (fixed) text as commit message?

---8<---8<---

Mistakenly the buffers (input and output) become together enabled for a short
period of time during GPIO request. This is problematic, because instead of
initial motive to disable them in the commit af7e3eeb84e2
("pinctrl: intel: Disable input and output buffer when switching to GPIO"),
the driven value on the pin, which might be used as an IRQ line, brings
firmwares of some touch pads to an awkward state that needs a full power off
to recover. Fix this by, as stated in the culprit commit, disabling the buffers.

P.S. I'm looking at 5f4592bc20c8 in your pin control tree, fixes branch.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-12-08  9:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 17:59 [PATCH v1] pinctrl: intel: Actually disable Tx and Rx buffers on GPIO request Andy Shevchenko
2020-12-07 18:08 ` Andy Shevchenko
2020-12-08  8:34   ` Linus Walleij
2020-12-08  9:48     ` Andy Shevchenko [this message]
2020-12-08  9:50       ` Andy Shevchenko
2020-12-08 18:25         ` Andy Shevchenko
2020-12-08 15:38       ` Linus Walleij
2020-12-07 18:16 ` Mika Westerberg
2020-12-07 21:52   ` Pierre-Louis Bossart
2020-12-08  0:56 ` Kai-Heng Feng

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=20201208094853.GF4077@smile.fi.intel.com \
    --to=andy.shevchenko@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.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 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.