From: Linus Walleij <linus.walleij@linaro.org>
To: "Paller, Kim Seer" <KimSeer.Paller@analog.com>
Cc: "Nuno Sá" <noname.nuno@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] gpio: gpio-adg1414: New driver
Date: Thu, 27 Feb 2025 01:33:57 +0100 [thread overview]
Message-ID: <CACRpkdaMBpUNHQu4kW0s0pDJSZ3M2GvNB7mY7DbnYuboebtgbg@mail.gmail.com> (raw)
In-Reply-To: <PH0PR03MB71419BE3FCE2DAE8AB72B79EF9FB2@PH0PR03MB7141.namprd03.prod.outlook.com>
On Mon, Feb 17, 2025 at 8:02 AM Paller, Kim Seer
<KimSeer.Paller@analog.com> wrote:
> In my opinion, using the GPIO subsystem for the ADG1414 may be a better option
> given the intended use case. However, what do you suggest on how to proceed?
I think it's best to proceed with a GPIO driver unless someone has
better ideas.
Address my comments on the regmap use please!
Yours,
Linus Walleij
next prev parent reply other threads:[~2025-02-27 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 13:15 [PATCH v2 0/2] Add support for ADG1414 Serially-Controlled Octal SPST Switches Kim Seer Paller
2025-02-13 13:15 ` [PATCH v2 1/2] dt-bindings: gpio: add adg1414 Kim Seer Paller
2025-02-13 16:11 ` kernel test robot
2025-02-13 18:16 ` Krzysztof Kozlowski
2025-02-14 10:42 ` Linus Walleij
2025-02-13 13:15 ` [PATCH v2 2/2] gpio: gpio-adg1414: New driver Kim Seer Paller
2025-02-13 23:25 ` Linus Walleij
2025-02-14 13:17 ` Nuno Sá
2025-02-14 23:22 ` Linus Walleij
2025-02-16 14:30 ` Jonathan Cameron
2025-02-17 7:02 ` Paller, Kim Seer
2025-02-17 9:32 ` Nuno Sá
2025-02-27 0:33 ` Linus Walleij [this message]
2025-02-15 1:12 ` kernel test robot
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=CACRpkdaMBpUNHQu4kW0s0pDJSZ3M2GvNB7mY7DbnYuboebtgbg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=KimSeer.Paller@analog.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=robh@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).