From: Simon Glass <sjg@chromium.org>
To: Samuel Holland <samuel@sholland.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Andre Przywara <andre.przywara@arm.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Icenowy Zheng <icenowy@aosc.io>,
Jaehoon Chung <jh80.chung@samsung.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 3/4] gpio: sunxi: Implement .set_flags
Date: Sun, 24 Oct 2021 13:53:55 -0600 [thread overview]
Message-ID: <CAPnjgZ1KAX9vaYE3ggzaSgO+coNdvgECHQx2jY9KSvJUuCULdA@mail.gmail.com> (raw)
In-Reply-To: <20211021045258.30757-4-samuel@sholland.org>
On Wed, 20 Oct 2021 at 22:53, Samuel Holland <samuel@sholland.org> wrote:
>
> This, along with gpio_flags_xlate(), allows the GPIO driver to handle
> pull-up/down flags provided by consumer drivers or in the device tree.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
>
> drivers/gpio/sunxi_gpio.c | 62 +++++++++++++++++----------------------
> 1 file changed, 27 insertions(+), 35 deletions(-)
>
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2021-10-24 19:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 4:52 [PATCH 0/4] gpio: sunxi: Handle pin configuration flags Samuel Holland
2021-10-21 4:52 ` [PATCH 1/4] sunxi: gpio: Return void from setter functions Samuel Holland
2021-11-05 13:53 ` Heinrich Schuchardt
2021-10-21 4:52 ` [PATCH 2/4] sunxi: gpio: Add per-bank drive and pull setters Samuel Holland
2021-11-05 14:12 ` Heinrich Schuchardt
2022-01-30 1:11 ` Andre Przywara
2021-10-21 4:52 ` [PATCH 3/4] gpio: sunxi: Implement .set_flags Samuel Holland
2021-10-24 19:53 ` Simon Glass [this message]
2021-11-05 14:43 ` Heinrich Schuchardt
2021-11-05 21:46 ` Samuel Holland
2022-01-30 1:18 ` Andre Przywara
2021-10-21 4:52 ` [PATCH 4/4] mmc: sunxi: Use DM_GPIO flags to set pull-up Samuel Holland
2021-10-21 21:58 ` Jaehoon Chung
2021-10-22 9:00 ` Andre Przywara
2021-10-22 10:10 ` Jaehoon Chung
2021-10-22 10:36 ` Andre Przywara
2021-11-05 15:52 ` Heinrich Schuchardt
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=CAPnjgZ1KAX9vaYE3ggzaSgO+coNdvgECHQx2jY9KSvJUuCULdA@mail.gmail.com \
--to=sjg@chromium.org \
--cc=andre.przywara@arm.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=peng.fan@nxp.com \
--cc=samuel@sholland.org \
--cc=u-boot@lists.denx.de \
/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.