From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, edgari@xilinx.com, alistai@xilinx.com
Subject: Re: [Qemu-devel] [PATCH qom v5 2/2] ssi: Name the CS GPIO.
Date: Tue, 20 May 2014 11:53:09 +0200 [thread overview]
Message-ID: <537B2605.3070106@suse.de> (raw)
In-Reply-To: <7ce016cddf7fe218f1473649488ce147ccf65d31.1400567259.git.peter.crosthwaite@xilinx.com>
Am 20.05.2014 08:31, schrieb Peter Crosthwaite:
> 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,
I assumed you meant "in 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>
I've dropped the trailing dot from the subject. Please also remember to
place your Sob last.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-05-20 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 6:30 [Qemu-devel] [PATCH qom v5 0/2] Named GPIOs Peter Crosthwaite
2014-05-20 6:30 ` [Qemu-devel] [PATCH qom v5 1/2] qdev: Implement named GPIOs Peter Crosthwaite
2014-05-20 6:31 ` [Qemu-devel] [PATCH qom v5 2/2] ssi: Name the CS GPIO Peter Crosthwaite
2014-05-20 9:53 ` Andreas Färber [this message]
2014-05-20 22:08 ` Peter Crosthwaite
2014-05-20 9:49 ` [Qemu-devel] [PATCH qom v5 0/2] Named GPIOs Andreas Färber
2014-05-20 22:10 ` Peter Crosthwaite
2014-05-20 22:15 ` 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=537B2605.3070106@suse.de \
--to=afaerber@suse.de \
--cc=alistai@xilinx.com \
--cc=edgari@xilinx.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 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).