All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Mark Langsdorf <mark.langsdorf@calxeda.com>
Subject: Re: [Qemu-devel] [PATCH arm-devs v1 2/6] target-arm/cpu: Convert reset CBAR to a property
Date: Wed, 27 Nov 2013 11:27:51 +0100	[thread overview]
Message-ID: <5295C927.6040101@suse.de> (raw)
In-Reply-To: <CAFEAcA-7qpKdnvDwzZH13A2wG1iJqfNK9VdDVF9hS4F9SaAMsA@mail.gmail.com>

Am 27.11.2013 11:15, schrieb Peter Maydell:
> On 27 November 2013 09:42, Andreas Färber <afaerber@suse.de> wrote:
>> If we turn it into a dynamic property, we could register it conditional
>> to ARM_FEATURE_CBAR.
> 
> Unfortunately feature flags only get set at realize (in the
> per-cpu init function), so we don't know at the point where
> we're registering properties whether to have this one or not.

1/6 sets it in instance_init actually. So instance_post_init might do.

> The other option would be to define an a9 cpu class init fn to
> put the property in.

Is it A9-only or would A15, A7, A12, etc. also need it?

>> The overall idea of the series makes sense to me. I would caution to
>> think about the naming scheme though - we might want to have a "cbar"
>> property to access the current value whereas we'll likely end up having
>> several reset values to configure over time.
> 
> Mmm, maybe. The approach I think we've taken in some other
> places (eg the cache controller) is to have the property names
> match the silicon's config or control signal names (which in
> this case would be PERIPHBASE), but they are not always
> consistent from CPU to CPU, so that might be more confusing
> than helpful. I don't think I have a strong opinion here, so I'd
> be happy with any vaguely consistent-looking plan.

Whatever name you choose, I was rather thinking of whether you may want
to call it, e.g., "foo-reset" or "reset-foo" to distinguish from plain
"foo". (Igor's x86 properties series uses "feat-foo" on Anthony's
suggestion to group and parse feature properties.)

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-11-27 10:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  9:00 [Qemu-devel] [PATCH arm-devs v1 0/6] Fix Support for ARM A9 CBAR Peter Crosthwaite
2013-11-27  9:01 ` [Qemu-devel] [PATCH arm-devs v1 1/6] target-arm: Define and use ARM_FEATURE_CBAR Peter Crosthwaite
2013-11-27  9:01 ` [Qemu-devel] [PATCH arm-devs v1 2/6] target-arm/cpu: Convert reset CBAR to a property Peter Crosthwaite
2013-11-27  9:14   ` Peter Maydell
2013-11-27  9:42     ` Andreas Färber
2013-11-27 10:15       ` Peter Maydell
2013-11-27 10:27         ` Andreas Färber [this message]
2013-11-27 10:35           ` Peter Maydell
2013-11-27 11:39           ` Peter Crosthwaite
2013-11-27 11:47             ` Peter Maydell
2013-11-28  1:48               ` Peter Crosthwaite
2013-11-27 13:10             ` Andreas Färber
2013-11-27  9:02 ` [Qemu-devel] [PATCH arm-devs v1 3/6] arm/highbank: Use object_new() rather than cpu_arm_init() Peter Crosthwaite
2013-11-27  9:10   ` Peter Maydell
2013-11-27  9:52     ` Andreas Färber
2013-11-27  9:02 ` [Qemu-devel] [PATCH arm-devs v1 4/6] arm/highbank: Fix CBAR intialisation Peter Crosthwaite
2013-11-27  9:03 ` [Qemu-devel] [PATCH arm-devs v1 5/6] arm/xilinx_zynq: Use object_new() rather than cpu_arm_init() Peter Crosthwaite
2013-11-27  9:04 ` [Qemu-devel] [PATCH arm-devs v1 6/6] arm/xilinx_zynq: Implement CBAR intialisation Peter Crosthwaite

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=5295C927.6040101@suse.de \
    --to=afaerber@suse.de \
    --cc=imammedo@redhat.com \
    --cc=mark.langsdorf@calxeda.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.