From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 RESEND 3/5] spi: s3c64xx: Added provision for non-gpio i/o's
Date: Tue, 16 Apr 2013 16:58:50 +0100 [thread overview]
Message-ID: <20130416155850.GL26958@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366015230-18243-2-git-send-email-ks.giri@samsung.com>
On Mon, Apr 15, 2013 at 02:10:28PM +0530, Girish K S wrote:
> From: Girish K S <girishks2000@gmail.com>
>
> Currently the drivers supports only the GPIO based i/o pins.
> But there are Exynos SoC's that use the same controller with
> dedicated i/o pins.
>
> This patch provides provision to support gpio/dedicated pins.
> The decision is made by parsing the "gpios" property in the spi
> node.
This has some conflicts with my SPI -next branch, I think it's all due
to Arnd's changes to support multi-platform boot on Exynos but there may
be some other stuff. Can you please rebase against
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git spi-next
and make sure everything is OK?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130416/bda0d1b0/attachment.sig>
next prev parent reply other threads:[~2013-04-16 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 8:40 [PATCH V4 2/5] spi: s3c64xx: added support for polling mode Girish K S
2013-04-15 8:40 ` [PATCH V3 RESEND 3/5] spi: s3c64xx: Added provision for non-gpio i/o's Girish K S
2013-04-16 15:58 ` Mark Brown [this message]
2013-04-15 8:40 ` [PATCH V4 4/5] spi: s3c64xx: Added provision for dedicated cs pin Girish K S
2013-04-15 8:40 ` [PATCH RESEND V3 5/5] spi: s3c64xx: Added support for exynos5440 spi Girish K S
2013-04-16 11:20 ` [PATCH V4 2/5] spi: s3c64xx: added support for polling mode Mark Brown
2013-04-16 11:28 ` Girish KS
2013-04-16 12:12 ` Mark Brown
2013-04-17 10:22 ` Girish KS
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=20130416155850.GL26958@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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