From: Corey Minyard <minyard@acm.org>
To: Titus Rwantare <titusr@google.com>
Cc: philmd@linaro.org, qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Hao Wu <wuhaotsh@google.com>
Subject: Re: [PATCH 1/5] hw/i2c: pmbus add support for block receive
Date: Thu, 30 Mar 2023 11:18:36 -0500 [thread overview]
Message-ID: <ZCW2XDxAzptykEQf@minyard.net> (raw)
In-Reply-To: <20230322175513.1550412-2-titusr@google.com>
It's generally frowned upon to have empty descriptions, some rationale
would be helpful. For instance, you remove a length check from the send
string, why did you do that?
Any why is this being added? What's it supporting?
-corey
On Wed, Mar 22, 2023 at 05:55:09PM +0000, Titus Rwantare wrote:
> Reviewed-by: Hao Wu <wuhaotsh@google.com>
> Signed-off-by: Titus Rwantare <titusr@google.com>
> ---
> hw/i2c/pmbus_device.c | 30 +++++++++++++++++++++++++++++-
> include/hw/i2c/pmbus_device.h | 7 +++++++
> 2 files changed, 36 insertions(+), 1 deletion(-)
>
> diff --git a/hw/i2c/pmbus_device.c b/hw/i2c/pmbus_device.c
> index c3d6046784..02647769cd 100644
> --- a/hw/i2c/pmbus_device.c
> +++ b/hw/i2c/pmbus_device.c
> @@ -95,7 +95,6 @@ void pmbus_send64(PMBusDevice *pmdev, uint64_t data)
> void pmbus_send_string(PMBusDevice *pmdev, const char *data)
> {
> size_t len = strlen(data);
> - g_assert(len > 0);
> g_assert(len + pmdev->out_buf_len < SMBUS_DATA_MAX_LEN);
> pmdev->out_buf[len + pmdev->out_buf_len] = len;
>
> @@ -105,6 +104,35 @@ void pmbus_send_string(PMBusDevice *pmdev, const char *data)
> pmdev->out_buf_len += len + 1;
> }
>
> +uint8_t pmbus_receive_block(PMBusDevice *pmdev, uint8_t *dest, size_t len)
> +{
> + /* dest may contain data from previous writes */
> + memset(dest, 0, len);
> +
> + /* Exclude command code from return value */
> + pmdev->in_buf++;
> + pmdev->in_buf_len--;
> +
> + /* The byte after the command code denotes the length */
> + uint8_t sent_len = pmdev->in_buf[0];
> +
> + if (sent_len != pmdev->in_buf_len - 1) {
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "%s: length mismatch. Expected %d bytes, got %d bytes\n",
> + __func__, sent_len, pmdev->in_buf_len - 1);
> + }
> +
> + /* exclude length byte */
> + pmdev->in_buf++;
> + pmdev->in_buf_len--;
> +
> + if (pmdev->in_buf_len < len) {
> + len = pmdev->in_buf_len;
> + }
> + memcpy(dest, pmdev->in_buf, len);
> + return len;
> +}
> +
>
> static uint64_t pmbus_receive_uint(PMBusDevice *pmdev)
> {
> diff --git a/include/hw/i2c/pmbus_device.h b/include/hw/i2c/pmbus_device.h
> index 93f5d57c9d..7dc00cc4d9 100644
> --- a/include/hw/i2c/pmbus_device.h
> +++ b/include/hw/i2c/pmbus_device.h
> @@ -501,6 +501,13 @@ void pmbus_send64(PMBusDevice *state, uint64_t data);
> */
> void pmbus_send_string(PMBusDevice *state, const char *data);
>
> +/**
> + * @brief Receive data sent with Block Write.
> + * @param dest - memory with enough capacity to receive the write
> + * @param len - the capacity of dest
> + */
> +uint8_t pmbus_receive_block(PMBusDevice *pmdev, uint8_t *dest, size_t len);
> +
> /**
> * @brief Receive data over PMBus
> * These methods help track how much data is being received over PMBus
> --
> 2.40.0.rc1.284.g88254d51c5-goog
>
next prev parent reply other threads:[~2023-03-30 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 17:55 [PATCH 0/5] PMBus fixes and new functions Titus Rwantare
2023-03-22 17:55 ` [PATCH 1/5] hw/i2c: pmbus add support for block receive Titus Rwantare
2023-03-30 16:18 ` Corey Minyard [this message]
2023-03-31 0:05 ` Titus Rwantare
2023-03-22 17:55 ` [PATCH 2/5] hw/i2c: pmbus: add vout mode bitfields Titus Rwantare
2023-03-30 16:20 ` Corey Minyard
2023-03-30 16:25 ` Corey Minyard
2023-03-22 17:55 ` [PATCH 3/5] hw/i2c: pmbus: add fan support Titus Rwantare
2023-03-30 16:22 ` Corey Minyard
2023-03-22 17:55 ` [PATCH 4/5] hw/i2c: pmbus: block uninitialised string reads Titus Rwantare
2023-03-29 14:15 ` Philippe Mathieu-Daudé
2023-03-30 16:23 ` Corey Minyard
2023-03-22 17:55 ` [PATCH 5/5] hw/i2c: pmbus: add VCAP register Titus Rwantare
2023-03-30 16:25 ` Corey Minyard
2023-03-30 14:24 ` [PATCH 0/5] PMBus fixes and new functions Philippe Mathieu-Daudé
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=ZCW2XDxAzptykEQf@minyard.net \
--to=minyard@acm.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=titusr@google.com \
--cc=wuhaotsh@google.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).