qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "~fvanhovell" <frederik@fvhovell.nl>,
	qemu-trivial@nongnu.org,  Cryptjar <cryptjar@junk.studio>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH qemu] [hw/char/bcm2835_aux] Fix receive FIFO filling up (raspi3)
Date: Thu, 25 Jul 2024 15:39:25 +0100	[thread overview]
Message-ID: <CAFEAcA8m0V3eExzzoZwoxrs38bt_pkmPm9nB4ybjWteh5q3DSA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_A57pCQEHi_oSMvngQggfcbW9pR9+qkyQm49NQiVREnQ@mail.gmail.com>

On Mon, 22 Jul 2024 at 10:44, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> [Added missing cc of qemu-devel]
>
> On Mon, 22 Jul 2024 at 07:33, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> >
> > On 21/7/24 18:13, ~fvanhovell wrote:
> > > From: Frederik van Hövell <frederik@fvhovell.nl>
> > >
> > > When a bare-metal application on the raspi3 board reads the
> > > AUX_MU_STAT_REG MMIO register while the device's buffer is
> > > at full receive FIFO capacity
> > > (i.e. `s->read_count == BCM2835_AUX_RX_FIFO_LEN`) the
> > > assertion `assert(s->read_count < BCM2835_AUX_RX_FIFO_LEN)`
> > > fails.
> > >
> >
> > Reported-by: Cryptjar <cryptjar@junk.studio>
> > Suggested-by: Cryptjar <cryptjar@junk.studio>
> > Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> >
> > > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/459
> > > Signed-off-by: Frederik van Hövell <frederik@fvhovell.nl>
> > > ---
> > >   hw/char/bcm2835_aux.c | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/hw/char/bcm2835_aux.c b/hw/char/bcm2835_aux.c
> > > index 83990e20f7..fca2f27a55 100644
> > > --- a/hw/char/bcm2835_aux.c
> > > +++ b/hw/char/bcm2835_aux.c
> > > @@ -138,7 +138,7 @@ static uint64_t bcm2835_aux_read(void *opaque, hwaddr offset, unsigned size)
> > >           res = 0x30e; /* space in the output buffer, empty tx fifo, idle tx/rx */
> > >           if (s->read_count > 0) {
> > >               res |= 0x1; /* data in input buffer */
> > > -            assert(s->read_count < BCM2835_AUX_RX_FIFO_LEN);
> > > +            assert(s->read_count <= BCM2835_AUX_RX_FIFO_LEN);
> > >               res |= ((uint32_t)s->read_count) << 16; /* rx fifo fill level */
> > >           }
> > >           return res;
> >




Applied to target-arm.next, thanks.

-- PMM


      reply	other threads:[~2024-07-25 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172158154072.9480.4077116485578955977-0@git.sr.ht>
     [not found] ` <4100ce91-e4e0-426a-8098-93cd29e634ec@linaro.org>
2024-07-22  9:44   ` [PATCH qemu] [hw/char/bcm2835_aux] Fix receive FIFO filling up (raspi3) Peter Maydell
2024-07-25 14:39     ` Peter Maydell [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=CAFEAcA8m0V3eExzzoZwoxrs38bt_pkmPm9nB4ybjWteh5q3DSA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=cryptjar@junk.studio \
    --cc=frederik@fvhovell.nl \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).