From: Drew Fustini <fustini@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Michael Ellerman <mpe@kernel.org>,
linux-riscv@lists.infradead.org, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>
Subject: Re: [PATCH] riscv: defconfig: thead: enable PCA953X GPIO driver
Date: Fri, 5 Jun 2026 09:57:43 -0700 [thread overview]
Message-ID: <aiMAB0RjnjEzDQKu@x1> (raw)
In-Reply-To: <7ffb4a7c-ea74-431a-8be9-1a1d7418b467@kernel.org>
On Fri, Jun 05, 2026 at 02:50:54PM +1000, Michael Ellerman wrote:
> On 3/6/26 6:21 pm, Marek Szyprowski wrote:
> > Enable PCA953X GPIO driver to properly probe Wifi pwrseq driver on
> > LicheePi4a board.
> >
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > ---
> > arch/riscv/configs/defconfig | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
> > index 08445df56006..a51a423d53f4 100644
> > --- a/arch/riscv/configs/defconfig
> > +++ b/arch/riscv/configs/defconfig
> > @@ -174,6 +174,8 @@ CONFIG_PINCTRL_SOPHGO_SG2002=y
> > CONFIG_GPIO_DWAPB=y
> > CONFIG_GPIO_SIFIVE=y
> > CONFIG_GPIO_SPACEMIT_K1=y
> > +CONFIG_GPIO_PCA953X=y
> > +CONFIG_GPIO_PCA953X_IRQ=y
> Does it need to be built-in, or would a module work?
>
> It's not a huge driver (~20KB), but it all adds up.
Good point.
Marek - could you respin as module?
thanks,
drew
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-06-05 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260603082156eucas1p1f44a198f7957d9d82ec0b8bc296fb03c@eucas1p1.samsung.com>
2026-06-03 8:21 ` [PATCH] riscv: defconfig: thead: enable PCA953X GPIO driver Marek Szyprowski
2026-06-03 19:39 ` Drew Fustini
2026-06-04 9:41 ` Conor Dooley
2026-06-05 4:50 ` Michael Ellerman
2026-06-05 16:57 ` Drew Fustini [this message]
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=aiMAB0RjnjEzDQKu@x1 \
--to=fustini@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=mpe@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=wefu@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox