qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: "Edgar Iglesias" <edgari@xilinx.com>,
	alistai@xilinx.com, "QEMU Developers" <qemu-devel@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] ssi: Name the CS GPIO.
Date: Fri, 9 May 2014 17:56:20 +0100	[thread overview]
Message-ID: <CAFEAcA_-EU+e5vL0RMSW8qd8ANb_5HtU8sXRpgkkG8hT_cV_uw@mail.gmail.com> (raw)
In-Reply-To: <ab75d5f22ac2ef1bc160e3de99101b50b314bb66.1399532194.git.peter.crosthwaite@xilinx.com>

On 8 May 2014 07:59, Peter Crosthwaite <peter.crosthwaite@xilinx.com> wrote:
> To get it out of the default GPIO list. This allows child devices to
> use the un-named GPIO namespace without having to be SSI aware. That
> is, there is no more need for machines to know about the obscure
> policy where GPIO 0 is the SSI chip-select and GPIO 1..N are the
> concrete class GPIOs (defined locally as 0..N-1).
>
> This is most notable is stellaris, which uses a device which has both
> SSI and concrete level GPIOs.
>
> Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>

Reviewed-by: Peter Maydell <peter.maydell@linaro.org>

-- PMM

      reply	other threads:[~2014-05-09 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  6:58 [Qemu-devel] [PATCH v3 0/2] Named GPIOs Peter Crosthwaite
2014-05-08  6:59 ` [Qemu-devel] [PATCH v3 1/2] qdev: Implement named GPIOs Peter Crosthwaite
2014-05-09 16:52   ` Peter Maydell
2014-05-12  1:09     ` Peter Crosthwaite
2014-05-08  6:59 ` [Qemu-devel] [PATCH v3 2/2] ssi: Name the CS GPIO Peter Crosthwaite
2014-05-09 16:56   ` 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=CAFEAcA_-EU+e5vL0RMSW8qd8ANb_5HtU8sXRpgkkG8hT_cV_uw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=alistai@xilinx.com \
    --cc=edgari@xilinx.com \
    --cc=peter.crosthwaite@xilinx.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).