From: Alistair Francis <alistair.francis@xilinx.com>
To: P J P <ppandit@redhat.com>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm <qemu-arm@nongnu.org>, Huawei PSIRT <psirt@huawei.com>,
	Qemu Developers <qemu-devel@nongnu.org>,
	"Edgar E . Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] char: cadence: check baud rate generator and divider values
Date: Wed, 26 Oct 2016 11:51:24 -0700	[thread overview]
Message-ID: <CAKmqyKOeT3eEOkjdnxN-fd_Ubnn+kjD_cr2eT-+LxHPKQg8SdA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1610261210330.21732@wniryva>
On Tue, Oct 25, 2016 at 11:50 PM, P J P <ppandit@redhat.com> wrote:
> +-- On Tue, 25 Oct 2016, Alistair Francis wrote --+
> | I think your email crossed with Peter. Have a look at what he said.
> | That should clarify everything.
>
>   I saw, I'll mask values with 0xFFFF and 0xFF; But it's not clear if ignoring
> values 0 - 3, means leaving registers uninitialised and adding checks at each
> usage point to ensure their value is valid. If so, do we return from
> uart_parameters_setup(), when either value is invalid ? Earlier you'd
> suggested using default values
>
>   -> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg04397.html
>From what I can tell I would say that any writes to the divider
register that have a value lower then 3 are ignored and the register
isn't updated.
That way we will always have a valid value as the register is reset to 0xF.
Thanks,
Alistair
>
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
>
next prev parent reply	other threads:[~2016-10-26 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 13:22 [Qemu-devel] [PATCH v2] char: cadence: check baud rate generator and divider values P J P
2016-10-25 17:22 ` Alistair Francis
2016-10-25 18:24   ` P J P
2016-10-25 22:29     ` Alistair Francis
2016-10-26  6:50       ` P J P
2016-10-26 18:51         ` Alistair Francis [this message]
2016-10-26 21:23           ` P J P
2016-10-25 17:55 ` Peter Maydell
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=CAKmqyKOeT3eEOkjdnxN-fd_Ubnn+kjD_cr2eT-+LxHPKQg8SdA@mail.gmail.com \
    --to=alistair.francis@xilinx.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=ppandit@redhat.com \
    --cc=psirt@huawei.com \
    --cc=qemu-arm@nongnu.org \
    --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).