From: Peter Maydell <peter.maydell@linaro.org>
To: Roy Franz <roy.franz@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] block: mask NOR flash buffered write length
Date: Fri, 18 Oct 2013 15:11:00 +0100 [thread overview]
Message-ID: <CAFEAcA_iaAgAtmaLjoaFZMgGJ5kj4nHxcvqOPZ=QT1tueNVSug@mail.gmail.com> (raw)
In-Reply-To: <CAFECyb_uLvn-moZ8B_5FnfOWFp06QLm_dkK3-y5JApGBemMXHg@mail.gmail.com>
On 18 October 2013 15:05, Roy Franz <roy.franz@linaro.org> wrote:
> On Fri, Oct 18, 2013 at 7:01 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> Yes, you should make the default for the device-width property
>> be to be the same as the bank-width, since that's what we
>> currently implement; then we can just change the platforms
>> where we know that's wrong.
>>
>> NB: probably best to leave the existing 'width' property with
>> the name it has, rather than renaming it to 'bank-width'.
> Thanks Peter. I'm not familiar with the "properties" and how they are
> used. I think that
> the device width is likely only of interest internally, so I won't add
> a device-width property.
No, you need to add a property. Properties are how all configurable
device parameters are set: if you look at the implementation
of the pflash_cfi01_register() function you'll see that it's
just a convenience wrapper that creates the device and sets a
lot of properties on it. device-width should be one of those,
in the same way as the existing width property.
In fact I would suggest that you don't change the utility
pflash_cfi01_register() function to add a new parameter to
it (that would involve editing every caller). Instead just
opencode the "create / set properties / init / map" sequence
in vexpress.c. I think that will actually be easier to read
since you don't have to match up each unnamed argument in
a long function call with what it actually does.
-- PMM
next prev parent reply other threads:[~2013-10-18 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 2:30 [Qemu-devel] [PATCH] block: mask NOR flash buffered write length Roy Franz
2013-10-18 11:38 ` Stefan Hajnoczi
2013-10-18 13:36 ` Peter Maydell
2013-10-18 13:54 ` Roy Franz
2013-10-18 14:01 ` Peter Maydell
2013-10-18 14:05 ` Roy Franz
2013-10-18 14:11 ` Peter Maydell [this message]
2013-10-18 14:14 ` Roy Franz
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='CAFEAcA_iaAgAtmaLjoaFZMgGJ5kj4nHxcvqOPZ=QT1tueNVSug@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=kwolf@redhat.com \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=roy.franz@linaro.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.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).