From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Anders Berg <anders.berg@avagotech.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 1/2] gpio: Add driver for AXM55xx SSP chip selects
Date: Fri, 5 Sep 2014 10:47:47 +0100 [thread overview]
Message-ID: <20140905094747.GE30401@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1409576021-24828-2-git-send-email-anders.berg@avagotech.com>
On Mon, Sep 01, 2014 at 02:53:40PM +0200, Anders Berg wrote:
> The AXM55xx device has a ARM PL022 SSP controller with an extension that
> enables the control of up to five chip select signals. This driver implements
> the logic to control these signals and exports them as GPIOs.
>
> Signed-off-by: Anders Berg <anders.berg@avagotech.com>
So, what happens if the GPIO driver binds first, followed by the SSP
device? Please test that scenario out before this patch gets merged.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-09-05 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 12:53 [PATCH 0/2] Add driver for AXM55xx SSP chip selects Anders Berg
2014-09-01 12:53 ` [PATCH 1/2] gpio: " Anders Berg
2014-09-04 17:04 ` Linus Walleij
[not found] ` <CACRpkdby4H-fivNn_kG2uL0EjsCGAc+t6OyFi0+VcNGf2Z9NQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 17:06 ` Mark Brown
2014-09-04 17:32 ` Linus Walleij
2014-09-05 9:05 ` Anders Berg
2014-09-06 13:53 ` Mark Brown
[not found] ` <20140906135308.GC2601-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-09-08 11:02 ` Anders Berg
2014-09-08 11:35 ` Mark Brown
2014-09-05 9:47 ` Russell King - ARM Linux [this message]
2014-09-05 13:40 ` Anders Berg
2014-09-01 12:53 ` [PATCH 2/2] Documentation: DT bindings for AXM55xx SSP CS Anders Berg
2014-09-04 17:05 ` Linus Walleij
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=20140905094747.GE30401@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=anders.berg@avagotech.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).