From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dipen Patel <dipenp@nvidia.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
timestamp@lists.linux.dev, linux-tegra@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups
Date: Tue, 10 Oct 2023 18:17:05 +0300 [thread overview]
Message-ID: <20231010151709.4104747-1-andriy.shevchenko@linux.intel.com> (raw)
This is a series provides a new API to GPIO library (so far only
available in the GPIO tree), and respective update to the Tegra
HTE driver. On top a couple of other cleaups (patches 3 & 4, they
can be applied separately).
Patch 2 inherited tags from its respective discussion thread [1],
but I believe the Tested-by needs to be confirmed again.
Due to dependencies this either should be applied to the GPIO tree,
or to the HTE when GPIO updates land the upstream (optionally with
the first patch be applied even now to the GPIO tree independently).
Another option is to have an immutable branch or tag, but I assume
that was discussed and rejected (?) in [1].
Link: https://lore.kernel.org/linux-gpio/20230905185309.131295-15-brgl@bgdev.pl/ [1]
Cc: Dipen Patel <dipenp@nvidia.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Andy Shevchenko (3):
gpiolib: provide gpio_device_find_by_fwnode()
hte: tegra194: Remove redundant dev_err()
hte: tegra194: Switch to LATE_SIMPLE_DEV_PM_OPS()
Bartosz Golaszewski (1):
hte: tegra194: don't access struct gpio_chip
drivers/gpio/gpiolib.c | 20 ++++++++++++++++
drivers/hte/hte-tegra194.c | 46 +++++++++++++++++++------------------
include/linux/gpio/driver.h | 1 +
3 files changed, 45 insertions(+), 22 deletions(-)
--
2.40.0.1.gaa8946217a0b
next reply other threads:[~2023-10-10 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:17 Andy Shevchenko [this message]
2023-10-10 15:17 ` [PATCH v1 1/4] gpiolib: provide gpio_device_find_by_fwnode() Andy Shevchenko
2023-10-13 9:21 ` Linus Walleij
2023-10-10 15:17 ` [PATCH v1 2/4] hte: tegra194: don't access struct gpio_chip Andy Shevchenko
2023-10-10 16:19 ` Dipen Patel
2023-10-10 19:31 ` Dipen Patel
2023-10-11 5:54 ` Andy Shevchenko
2023-10-11 18:05 ` Dipen Patel
2023-10-10 15:17 ` [PATCH v1 3/4] hte: tegra194: Remove redundant dev_err() Andy Shevchenko
2023-10-11 2:19 ` Dipen Patel
2023-10-10 15:17 ` [PATCH v1 4/4] hte: tegra194: Switch to LATE_SIMPLE_DEV_PM_OPS() Andy Shevchenko
2023-10-10 19:36 ` Dipen Patel
2023-10-11 5:55 ` Andy Shevchenko
2023-10-11 18:06 ` Dipen Patel
2023-10-11 9:33 ` [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups Bartosz Golaszewski
2023-10-11 10:06 ` Andy Shevchenko
2023-10-11 18:04 ` Dipen Patel
2023-10-11 11:43 ` 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=20231010151709.4104747-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dipenp@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=timestamp@lists.linux.dev \
/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).