From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] spi: s3c64xx: Added provision for dedicated cs pin
Date: Tue, 23 Apr 2013 15:42:56 +0100 [thread overview]
Message-ID: <20130423144256.GP5019@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366614565-3743-3-git-send-email-ks.giri@samsung.com>
On Mon, Apr 22, 2013 at 12:39:24PM +0530, Girish K S wrote:
> From: Girish K S <girishks2000@gmail.com>
>
> The existing driver supports gpio based /cs signal.
> For controller's that have one device per controller,
> the slave device's /cs signal might be internally controlled
> by the chip select bit of slave select register. They are not
> externally asserted/deasserted using gpio pin.
This doesn't build:
drivers/spi/spi-s3c64xx.c: In function 's3c64xx_get_slave_ctrldata':
drivers/spi/spi-s3c64xx.c:1023: error: 'sdd' undeclared (first use in this function)
drivers/spi/spi-s3c64xx.c:1023: error: (Each undeclared identifier is reported only once
drivers/spi/spi-s3c64xx.c:1023: error: for each function it appears in.)
-------------- 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/20130423/ab4c606f/attachment.sig>
next prev parent reply other threads:[~2013-04-23 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 7:09 [PATCH 0/3] Polling support for s3c64xx spi controller Girish K S
2013-04-22 7:09 ` [PATCH 1/3] spi: s3c64xx: added support for polling mode Girish K S
2013-04-23 15:15 ` Mark Brown
2013-04-24 9:37 ` Girish KS
2013-04-22 7:09 ` [PATCH 2/3] spi: s3c64xx: Added provision for dedicated cs pin Girish K S
2013-04-23 14:42 ` Mark Brown [this message]
2013-04-24 9:39 ` Girish KS
2013-04-22 7:09 ` [PATCH 3/3] spi: s3c64xx: Added support for exynos5440 spi Girish K S
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=20130423144256.GP5019@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;
as well as URLs for NNTP newsgroup(s).