linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Dong Aisheng <aisheng.dong@nxp.com>,
	Fabio Estevam <festevam@gmail.com>,
	Shawn Guo <shawnguo@kernel.org>, Jacky Bai <ping.bai@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Chester Lin <chester62515@gmail.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org, NXP S32 Linux Team <s32@nxp.com>,
	Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
Subject: [PATCH 0/3] add small improvements to the S32G pinctrl driver
Date: Tue, 23 Jul 2024 16:18:29 +0300	[thread overview]
Message-ID: <20240723131832.1171036-1-andrei.stefanescu@oss.nxp.com> (raw)

This patch series adds various small improvements to the pinctrl
driver used by S32G SoCs. These can also be found in the
downstream kernel version [1].

[1] - https://github.com/nxp-auto-linux/linux

Andrei Stefanescu (3):
  pinctrl: s32cc: enable the input buffer for a GPIO
  pinctrl: s32cc: configure PIN_CONFIG_DRIVE_PUSH_PULL
  pinctrl: s32cc: add update and overwrite options when setting pinconf

 drivers/pinctrl/nxp/pinctrl-s32cc.c | 51 ++++++++++++++++++++---------
 1 file changed, 35 insertions(+), 16 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-07-23 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 13:18 Andrei Stefanescu [this message]
2024-07-23 13:18 ` [PATCH 1/3] pinctrl: s32cc: enable the input buffer for a GPIO Andrei Stefanescu
2024-07-23 13:18 ` [PATCH 2/3] pinctrl: s32cc: configure PIN_CONFIG_DRIVE_PUSH_PULL Andrei Stefanescu
2024-07-23 13:18 ` [PATCH 3/3] pinctrl: s32cc: add update and overwrite options when setting pinconf Andrei Stefanescu
2024-08-05  8:18 ` [PATCH 0/3] add small improvements to the S32G pinctrl driver 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=20240723131832.1171036-1-andrei.stefanescu@oss.nxp.com \
    --to=andrei.stefanescu@oss.nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=chester62515@gmail.com \
    --cc=festevam@gmail.com \
    --cc=ghennadi.procopciuc@oss.nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbrugger@suse.com \
    --cc=ping.bai@nxp.com \
    --cc=s32@nxp.com \
    --cc=shawnguo@kernel.org \
    /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 NNTP newsgroup(s).