From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux pin control <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [GIT PULL] intel-pinctrl for 6.9-1
Date: Thu, 25 Apr 2024 15:14:06 +0300 [thread overview]
Message-ID: <ZipJDvhxihtpiCgN@black.fi.intel.com> (raw)
Hi Linux pin control maintainers,
A couple of GPIO mode fixes for Intel Bay Trail from Hans. This was a few weeks
in Linux Next without issues reported. Please, pull for v6.9-rcX.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v6.9-1
for you to fetch changes up to 5d10a157ebe02ac9b8abacfd529f8b045e8aa41b:
pinctrl: baytrail: Add pinconf group for uart3 (2024-04-08 17:54:48 +0300)
----------------------------------------------------------------
intel-pinctrl for v6.9-1
* Correct GPIO selection and add UART3 pins for Intel Bay Trail
The following is an automated git shortlog grouped by driver:
baytrail:
- Add pinconf group for uart3
- Fix selecting gpio pinctrl state
----------------------------------------------------------------
Hans de Goede (2):
pinctrl: baytrail: Fix selecting gpio pinctrl state
pinctrl: baytrail: Add pinconf group for uart3
drivers/pinctrl/intel/pinctrl-baytrail.c | 78 +++++++++++++++++---------------
drivers/pinctrl/intel/pinctrl-intel.h | 4 ++
2 files changed, 45 insertions(+), 37 deletions(-)
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2024-04-25 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:14 Andy Shevchenko [this message]
2024-04-25 13:32 ` [GIT PULL] intel-pinctrl for 6.9-1 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=ZipJDvhxihtpiCgN@black.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).