From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Glenn Miles <milesg@linux.vnet.ibm.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, clg@kaod.org, npiggin@gmail.com,
fbarrat@linux.ibm.com
Subject: Re: [PATCH v2 1/2] ppc/pnv: Add an I2C controller model
Date: Fri, 13 Oct 2023 10:58:30 +0200 [thread overview]
Message-ID: <31467531-ed8c-507e-1a39-3271fa375e59@linaro.org> (raw)
In-Reply-To: <20231012200851.3020858-2-milesg@linux.vnet.ibm.com>
Hi Glenn, Cédric,
On 12/10/23 22:08, Glenn Miles wrote:
> From: Cédric Le Goater <clg@kaod.org>
>
> The more recent IBM power processors have an embedded I2C
> controller that is accessible by software via the XSCOM
> address space.
>
> Each instance of the I2C controller is capable of controlling
> multiple I2C buses (one at a time). Prior to beginning a
> transaction on an I2C bus, the bus must be selected by writing
> the port number associated with the bus into the PORT_NUM
> field of the MODE register. Once an I2C bus is selected,
> the status of the bus can be determined by reading the
> Status and Extended Status registers.
>
> I2C bus transactions can be started by writing a command to
> the Command register and reading/writing data from/to the
> FIFO register.
>
> Not supported :
>
> . 10 bit I2C addresses
> . Multimaster
> . Slave
>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> [milesg: Split wiring to powernv9 into its own commit]
> [milesg: Added more detail to commit message]
> [milesg: Added SPDX Licensed Identifier to new files]
> [milesg: updated copyright dates]
> [milesg: Added use of g_autofree]
> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com>
> ---
>
> Changes in v2:
> - Updated copyright dates
> - Removed copyright paragraph (replaced by SPDX-License-Identifier)
> - Added use of g_autofree
>
> hw/ppc/meson.build | 1 +
> hw/ppc/pnv_i2c.c | 673 +++++++++++++++++++++++++++++++++++++
> include/hw/ppc/pnv_i2c.h | 38 +++
> include/hw/ppc/pnv_xscom.h | 3 +
> 4 files changed, 715 insertions(+)
> create mode 100644 hw/ppc/pnv_i2c.c
> create mode 100644 include/hw/ppc/pnv_i2c.h
> +/* I2C mode register */
> +#define I2C_MODE_REG 0x6
> +#define I2C_MODE_BIT_RATE_DIV PPC_BITMASK(0, 15)
> +#define I2C_MODE_PORT_NUM PPC_BITMASK(16, 21)
> +#define I2C_MODE_ENHANCED PPC_BIT(28)
> +#define I2C_MODE_DIAGNOSTIC PPC_BIT(29)
> +#define I2C_MODE_PACING_ALLOW PPC_BIT(30)
> +#define I2C_MODE_WRAP PPC_BIT(31)
> +static I2CBus *pnv_i2c_get_bus(PnvI2C *i2c)
> +{
> + uint8_t port = GETFIELD(I2C_MODE_PORT_NUM, i2c->regs[I2C_MODE_REG]);
> +
> + if (port >= i2c->num_busses) {
Can we sanitize in pnv_i2c_xscom_write() instead ...?
> + qemu_log_mask(LOG_GUEST_ERROR, "I2C: invalid bus number %d/%d\n", port,
> + i2c->num_busses);
> + return NULL;
> + }
> + return i2c->busses[port];
> +}
> +static void pnv_i2c_xscom_write(void *opaque, hwaddr addr,
> + uint64_t val, unsigned size)
> +{
> + PnvI2C *i2c = PNV_I2C(opaque);
> + uint32_t offset = addr >> 3;
> +
> + switch (offset) {
> + case I2C_MODE_REG:
... here?
> + i2c->regs[offset] = val;
> + if (i2c_bus_busy(pnv_i2c_get_bus(i2c))) {
> + i2c->regs[I2C_STAT_REG] |= I2C_STAT_INVALID_CMD;
> + qemu_log_mask(LOG_GUEST_ERROR, "I2C: command in progress\n");
> + }
> + break;
[...]
Regards,
Phil.
next prev parent reply other threads:[~2023-10-13 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 20:08 [PATCH v2 0/2] Add PowerNV I2C Controller Model Glenn Miles
2023-10-12 20:08 ` [PATCH v2 1/2] ppc/pnv: Add an I2C controller model Glenn Miles
2023-10-13 7:04 ` Cédric Le Goater
2023-10-16 17:42 ` Miles Glenn
2023-10-13 8:58 ` Philippe Mathieu-Daudé [this message]
2023-10-16 20:55 ` Miles Glenn
2023-10-17 6:57 ` Cédric Le Goater
2023-10-12 20:08 ` [PATCH v2 2/2] ppc/pnv: Connect I2C controller model to powernv9 chip Glenn Miles
2023-10-13 7:06 ` Cédric Le Goater
2023-10-16 17:44 ` Miles Glenn
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=31467531-ed8c-507e-1a39-3271fa375e59@linaro.org \
--to=philmd@linaro.org \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=milesg@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).