From: etanous via <qemu-devel@nongnu.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Joel Stanley" <joel@jms.id.au>, "Troy Lee" <leetroy@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Jamin Lin" <jamin_lin@aspeedtech.com>,
qemu-arm@nongnu.org, "Ed Tanous" <ed@tanous.net>,
"Patrick Williams" <patrick@stwcx.xyz>
Subject: Re: [PATCH 1/4] hw/arm: Add PCA9554 to ARM target
Date: Wed, 2 Jul 2025 12:20:55 -0700 [thread overview]
Message-ID: <aGWGl-9v4Nt9e2O1@edtanousvm.nvidia.com> (raw)
In-Reply-To: <e273f8c9-6479-4ae7-95a4-5f3a3053ad76@linaro.org>
On Wed, Jul 02, 2025 at 09:04:25AM +0200, Philippe Mathieu-Daudé wrote:
>
> Hi,
>
> On 2/7/25 08:47, Cédric Le Goater wrote:
> > Hello Ed,
> >
> > On 7/1/25 22:33, Ed Tanous wrote:
> > > From: Ed Tanous <ed@tanous.net>
> > >
> > > There are arm targets that are connected to this io expander,
> > > specifically some varieties of Aspeed 2600 BMCs. Add it to Kconfig to
> > > allow use.
> > >
> > > Signed-off-by: Ed Tanous <etanous@nvidia.com>
> > > ---
> > > hw/arm/Kconfig | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
> > > index f543d944c3..6ea86534d5 100644
> > > --- a/hw/arm/Kconfig
> > > +++ b/hw/arm/Kconfig
> > > @@ -532,6 +532,7 @@ config ASPEED_SOC
> > > select I2C
> > > select DPS310
> > > select PCA9552
> > > + select PCA9554
>
> Note, these i2c devices 1/ aren't part of the SoC, but boards/machines,
> 2/ nor are they required to have a functional machine (i.e. a i2c link
> could get cut or an i2c device ending dead).
>
> I'd prefer 1/ add a ASPEED_MACHINE layer selecting ASPEED_SOC and the
> external devices, and 2/ use "imply" statement instead of "select" for
> devices, as per docs/devel/kconfig.rst:
>
> Boards specify their constituent devices using ``imply`` and
> ``select`` directives. A device should be listed under ``select``
> if the board cannot be started at all without it. It should be
> listed under ``imply`` if (depending on the QEMU command line)
> the board may or may not be started without it. Boards default to
> true, but also have a ``depends on`` clause to limit them to the
> appropriate targets.
> For some targets, not all boards may be supported by hardware
> virtualization, in which case they also depend on the ``TCG``
> symbol, other symbols that are commonly used as dependencies for
> boards include libraries (such as ``FDT``) or ``TARGET_BIG_ENDIAN``
> (possibly negated).
>
ACK, seems reasonable. I tried to follow the pattern that was there,
but agreed, it was odd that "board" level things were added at the ARM
layer.
> My 2 cents.
>
> Regards,
>
> Phil.
next prev parent reply other threads:[~2025-07-02 19:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 20:33 [PATCH 0/4] Add support for gb200-bmc machine Ed Tanous
2025-07-01 20:33 ` [PATCH 1/4] hw/arm: Add PCA9554 to ARM target Ed Tanous
2025-07-02 6:47 ` Cédric Le Goater
2025-07-02 7:04 ` Philippe Mathieu-Daudé
2025-07-02 19:20 ` etanous via [this message]
2025-07-02 21:21 ` Cédric Le Goater
2025-07-02 19:18 ` etanous via
2025-07-01 20:33 ` [PATCH 2/4] hw/arm/aspeed: Add second SPI chip to Aspeed model Ed Tanous
2025-07-02 7:00 ` Cédric Le Goater
2025-07-02 19:27 ` etanous via
2025-07-02 21:23 ` Cédric Le Goater
2025-07-02 21:32 ` Cédric Le Goater
2025-07-01 20:33 ` [PATCH 3/4] docs: add support for gb200-bmc Ed Tanous
2025-07-02 6:49 ` Cédric Le Goater
2025-07-01 20:34 ` [PATCH 4/4] hw/arm/aspeed: Add GB200 BMC target Ed Tanous
2025-07-02 21:38 ` Cédric Le Goater
2025-07-02 22:04 ` Ed Tanous via
2025-07-02 7:00 ` [PATCH 0/4] Add support for gb200-bmc machine Cédric Le Goater
2025-07-02 19:31 ` etanous via
2025-07-02 21:25 ` Cédric Le Goater
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=aGWGl-9v4Nt9e2O1@edtanousvm.nvidia.com \
--to=qemu-devel@nongnu.org \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=ed@tanous.net \
--cc=etanous@nvidia.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=patrick@stwcx.xyz \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=steven_lee@aspeedtech.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;
as well as URLs for NNTP newsgroup(s).