From: Roger Quadros <rogerq@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
linux-omap@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
tony@atomide.com, devicetree@vger.kernel.org,
khilman@baylibre.com, Conor Dooley <conor+dt@kernel.org>,
aaro.koskinen@iki.fi
Subject: Re: [PATCH v2 4/4] ARM: dts: omap: omap4-epson-embt2ws: add GPIO expander
Date: Thu, 10 Oct 2024 23:17:13 +0300 [thread overview]
Message-ID: <8fd056d5-a357-4705-9352-632afcfe12fa@kernel.org> (raw)
In-Reply-To: <20241010122957.85164-5-andreas@kemnade.info>
On 10/10/2024 15:29, Andreas Kemnade wrote:
> Define the GPIO expander which controls at least some camera gpios.
>
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
next prev parent reply other threads:[~2024-10-10 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 12:29 [PATCH v2 0/4] ARM: dts: omap: omap4-epson-embt2ws: misc gpio definitions Andreas Kemnade
2024-10-10 12:29 ` [PATCH v2 1/4] ARM: dts: omap: omap4-epson-embt2ws: define GPIO regulators Andreas Kemnade
2024-10-10 20:07 ` Roger Quadros
2024-10-10 12:29 ` [PATCH v2 2/4] ARM: dts: omap: omap4-epson-embt2ws: wire up regulators Andreas Kemnade
2024-10-10 20:08 ` Roger Quadros
2024-10-10 12:29 ` [PATCH v2 3/4] ARM: dts: omap: omap4-epson-embt2ws: add unknown gpio outputs Andreas Kemnade
2024-10-10 20:15 ` Roger Quadros
2024-10-11 9:12 ` Andreas Kemnade
2024-10-11 10:37 ` Roger Quadros
2024-10-11 10:37 ` Roger Quadros
2024-10-10 12:29 ` [PATCH v2 4/4] ARM: dts: omap: omap4-epson-embt2ws: add GPIO expander Andreas Kemnade
2024-10-10 20:17 ` Roger Quadros [this message]
2024-10-10 14:30 ` [PATCH v2 0/4] ARM: dts: omap: omap4-epson-embt2ws: misc gpio definitions Rob Herring (Arm)
2024-10-17 9:49 ` Andreas Kemnade
2024-10-29 23:23 ` Kevin Hilman
2024-10-29 23:35 ` Kevin Hilman
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=8fd056d5-a357-4705-9352-632afcfe12fa@kernel.org \
--to=rogerq@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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.