linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 4/5] spi: s3c64xx: Added provision for dedicated cs pin
Date: Mon, 8 Apr 2013 11:15:30 +0100	[thread overview]
Message-ID: <20130408101530.GC9243@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAKrE-Kd+YAFmteDdh3odtV+YU1=OjoMuQV9usF4NmUse+TXhTg@mail.gmail.com>

On Mon, Apr 08, 2013 at 03:21:03PM +0530, Girish KS wrote:
> On Mon, Apr 1, 2013 at 6:27 PM, Mark Brown

> > It's also a bit odd that we end up checking cs_gpio and then using line
> > in the code, it'd be more idiomatic if cs_gpio were the GPIO number.

> In the original driver it was assumed that the cs line is always a gpio pin.
> But the current controller that i am working on has no gpio pin for cs
> selection.
> All the lines to the device are internally connected. There is no
> option to select
> the cs signal. So cs-gpio property parsing has to skipped for this
> controller, that means
> cs_gpio cannot be a GPIO number. If it has to be a number then it has
> to be < 0 to say
> it is not gpio. Any >= 0 number implies it is a valid gpio (in reality
> for this controller it is not.)

Two options here, one is to just assume nobody will use GPIO 0 and the
other is to set the number appopriately during probe so that only probe
needs to worry about the issue.
-------------- 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/20130408/8343d432/attachment.sig>

  reply	other threads:[~2013-04-08 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  6:43 [PATCH V3 0/5] Add polling support for 64xx spi controller Girish K S
2013-03-13  6:43 ` [PATCH V3 1/5] spi: s3c64xx: modified error interrupt handling and init Girish K S
2013-04-01 13:03   ` Mark Brown
2013-03-13  6:43 ` [PATCH V3 2/5] spi: s3c64xx: added support for polling mode Girish K S
2013-04-01 13:12   ` Mark Brown
2013-04-03 11:30     ` Girish KS
2013-04-03 11:49       ` Mark Brown
2013-04-04  5:45         ` Girish KS
2013-03-13  6:43 ` [PATCH V3 3/5] spi: s3c64xx: Added provision for non-gpio i/o's Girish K S
2013-03-13  6:43 ` [PATCH V3 4/5] spi: s3c64xx: Added provision for dedicated cs pin Girish K S
2013-04-01 12:57   ` Mark Brown
2013-04-08  9:51     ` Girish KS
2013-04-08 10:15       ` Mark Brown [this message]
2013-04-08 11:45         ` Girish KS
2013-04-08 11:52           ` Girish KS
2013-04-08 12:20           ` Mark Brown
2013-04-08 13:49             ` Girish KS
2013-04-09 10:34               ` Mark Brown
2013-03-13  6:43 ` [PATCH V3 5/5] spi: s3c64xx: Added support for exynos5440 spi Girish K S
2013-03-25  3:27 ` [PATCH V3 0/5] Add polling support for 64xx spi controller 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=20130408101530.GC9243@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --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).