From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alistair Francis" <alistair@alistair23.me>
Subject: Re: [Qemu-devel] [PATCH] hw/char/stm32f2xx_usart: Do not update data register when device is disabled
Date: Tue, 8 Jan 2019 11:53:47 +0000 [thread overview]
Message-ID: <CAFEAcA8z1c8=x3Ndrn2dRRJPaC_tUPQgWSRSsha57BoAnYHJoA@mail.gmail.com> (raw)
In-Reply-To: <20190104182057.8778-1-philmd@redhat.com>
On Fri, 4 Jan 2019 at 18:21, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> When the device is disable, the internal circuitry keep the data
> register loaded and doesn't update it.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> hw/char/stm32f2xx_usart.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/hw/char/stm32f2xx_usart.c b/hw/char/stm32f2xx_usart.c
> index f3363a2952..10392c70e2 100644
> --- a/hw/char/stm32f2xx_usart.c
> +++ b/hw/char/stm32f2xx_usart.c
> @@ -53,14 +53,13 @@ static void stm32f2xx_usart_receive(void *opaque, const uint8_t *buf, int size)
> {
> STM32F2XXUsartState *s = opaque;
>
> - s->usart_dr = *buf;
> -
> if (!(s->usart_cr1 & USART_CR1_UE && s->usart_cr1 & USART_CR1_RE)) {
> /* USART not enabled - drop the chars */
> DB_PRINT("Dropping the chars\n");
> return;
> }
>
> + s->usart_dr = *buf;
> s->usart_sr |= USART_SR_RXNE;
>
> if (s->usart_cr1 & USART_CR1_RXNEIE) {
> --
> 2.17.2
Applied to target-arm.next, thanks (with the commit message typos fixed).
-- PMM
prev parent reply other threads:[~2019-01-08 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 18:20 [Qemu-devel] [PATCH] hw/char/stm32f2xx_usart: Do not update data register when device is disabled Philippe Mathieu-Daudé
2019-01-04 18:31 ` Philippe Mathieu-Daudé
2019-01-04 19:47 ` Alistair Francis
2019-01-08 11:53 ` 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='CAFEAcA8z1c8=x3Ndrn2dRRJPaC_tUPQgWSRSsha57BoAnYHJoA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alistair@alistair23.me \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@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).