All of lore.kernel.org
 help / color / mirror / Atom feed
From: AceLan Kao <acelan.kao@canonical.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Mario.Limonciello@dell.com,
	Linus Walleij <linus.walleij@linaro.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Calvin Johnson <linux.cj@gmail.com>,
	Jared.Dominguez@dell.com, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] pinctrl: intel: Only restore pins that are used by the driver
Date: Tue, 11 Oct 2016 10:38:27 +0800	[thread overview]
Message-ID: <CAFv23QkWFkzGsUFEN5GW+47qQgNAtqSnXZeU_phos=J7czrKgQ@mail.gmail.com> (raw)
In-Reply-To: <CAFv23Qn+dDRyGutHBh0FfXRBZCmfTf_B0bQy-E-bb+4Nx+Xx2Q@mail.gmail.com>

Hi Mika,

BTW, I failed to compile the kernel 4.4 with the patch.

The patch uses gpiochip_line_is_irq() function which has been
introduced since 4.6-rc1, so we need to cherry pick this commit, too.
   6cee382 gpio/pinctrl: sunxi: stop poking around in private vars

But the above commit uses gpiodev data member in struct gpio_chip
which is introduced from this commit, and it's a big commit that can't
be cherry-picked clearly.
   ff2b135 gpio: make the gpiochip a real device

Will you provide other patch that can apply on top of old stable kernels?

AceLan Kao.

2016-10-11 9:31 GMT+08:00 AceLan Kao <acelan.kao@canonical.com>:
> Hi Mika,
>
> Yes, the patch works, the touchscreen continue working after lid close and open.
> Thanks for your work.
>
> Best regards,
> AceLan Kao.
>
> 2016-10-10 22:53 GMT+08:00 Mika Westerberg <mika.westerberg@linux.intel.com>:
>> On Mon, Oct 10, 2016 at 02:37:19PM +0000, Mario.Limonciello@dell.com wrote:
>>> After positive comments in this working properly and is accepted, would you
>>> consider submitting back to @stable as well?  It affects all kernel versions
>>> that carry intel pinctrl (IIRC back to 4.1?)
>>
>> Sure.
>>
>> LinusW, this should have stable tag starting from v4.1. Let me know if
>> you want me to re-submit the patch.

  reply	other threads:[~2016-10-11  2:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  5:57 [PATCH] pinctrl: intel: add blacklist list for XPS machines AceLan Kao
2016-10-05  7:57 ` Calvin Johnson
2016-10-05  8:55   ` Mika Westerberg
2016-10-05  9:23     ` AceLan Kao
2016-10-05  9:32       ` Mika Westerberg
2016-10-05 12:47         ` AceLan Kao
2016-10-10 13:39           ` [PATCH] pinctrl: intel: Only restore pins that are used by the driver Mika Westerberg
2016-10-10 14:37             ` Mario.Limonciello
2016-10-10 14:53               ` Mika Westerberg
2016-10-11  1:31                 ` AceLan Kao
2016-10-11  2:38                   ` AceLan Kao [this message]
2016-10-11  9:27                     ` Mika Westerberg
2016-10-12  1:35                       ` AceLan Kao
2016-10-18 12:39             ` Linus Walleij
2016-10-12 16:31 ` [PATCH] pinctrl: intel: add blacklist list for XPS machines Jon Masters
2016-10-18 12:43 ` Linus Walleij
2016-10-18 12:46   ` Mika Westerberg
2016-10-20 12:01     ` Linus Walleij

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='CAFv23QkWFkzGsUFEN5GW+47qQgNAtqSnXZeU_phos=J7czrKgQ@mail.gmail.com' \
    --to=acelan.kao@canonical.com \
    --cc=Jared.Dominguez@dell.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux.cj@gmail.com \
    --cc=mika.westerberg@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.