From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: AceLan Kao <acelan.kao@canonical.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 12:27:28 +0300 [thread overview]
Message-ID: <20161011092728.GE2774@lahna.fi.intel.com> (raw)
In-Reply-To: <CAFv23QkWFkzGsUFEN5GW+47qQgNAtqSnXZeU_phos=J7czrKgQ@mail.gmail.com>
On Tue, Oct 11, 2016 at 10:38:27AM +0800, AceLan Kao wrote:
> 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?
Hmm,
So 6cee382 ("gpio/pinctrl: sunxi: stop poking around in private vars")
needs the following patch.
I can backport 6cee382 with the below patch and send both patches to
stable@ after this gets merged to mainline but not sure if that's the
correct process to follow.
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index db007a3e2af7..6240dd40e8be 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1524,7 +1524,7 @@ bool gpiochip_line_is_irq(struct gpio_chip *chip, unsigned int offset)
if (offset >= chip->ngpio)
return false;
- return test_bit(FLAG_USED_AS_IRQ, &chip->gpiodev->descs[offset].flags);
+ return test_bit(FLAG_USED_AS_IRQ, &chip->desc[offset].flags);
}
EXPORT_SYMBOL_GPL(gpiochip_line_is_irq);
next prev parent reply other threads:[~2016-10-11 9:27 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
2016-10-11 9:27 ` Mika Westerberg [this message]
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=20161011092728.GE2774@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Jared.Dominguez@dell.com \
--cc=Mario.Limonciello@dell.com \
--cc=acelan.kao@canonical.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux.cj@gmail.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.