From: "Reizer, Eyal" <eyalr@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Eyal Reizer <eyalreizer@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: RE: [PATCHv2] wlcore: spi: add wl18xx support
Date: Tue, 19 Apr 2016 14:35:24 +0000 [thread overview]
Message-ID: <8665E2433BC68541A24DFFCA87B70F5B360C0C5D@DFRE01.ent.ti.com> (raw)
In-Reply-To: <4133521.UUI3B1RTyv@wuerfel>
> > > > It is also part of the generic spi.h (include/Linux/spi/spi.h),
> > > > already part of " struct spi_device" So it seemed redundant adding
> > > > another mechanism for implementing the same.
> > > > Platform that interact with a wilink need to use it, and platforms
> > > > that don't have this capability will probably not interact with a
> > > > wilink device
> > > using SPI.
> > >
> > > The cs_gpio field in spi_device belongs to the spi host controller,
> > > no other slave driver uses it.
> > >
> > > I wasn't asking for a duplication of this mechanism, but an
> > > interface to use it properly. Internally, the spi core uses the spi_set_cs()
> function to pick a CS.
> > > Find a way to use that rather than reimplementing it incorrectly.
> > >
> >
> > Understood. As this special CS manipulation is unique to wspi (wilink
> > spi) I think the best option is to move this gpio allocation into
> > wlcore_spi as a new device tree entry used only by this driver.
> > If you agree I will submit a v3.
>
> I don't think that can work either: aside of not solving the problem of wilink
> devices on spi controllers that don't use gpio, it also doesn't solve the
> problem of what happens when the driver manually triggers the gpio to hold
> the CS signal while another driver talks to a different device using another CS
> on the same controller.
>
Ok, understood. Will look into it.
Best Regards,
Eyal
next prev parent reply other threads:[~2016-04-19 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460273570-12298-1-git-send-email-eyalr@ti.com>
2016-04-10 7:37 ` Reizer, Eyal
2016-04-17 22:19 ` Arnd Bergmann
2016-04-18 5:55 ` Reizer, Eyal
2016-04-18 14:57 ` Arnd Bergmann
2016-04-19 9:05 ` Reizer, Eyal
2016-04-19 14:21 ` Arnd Bergmann
2016-04-19 14:35 ` Reizer, Eyal [this message]
2016-04-19 17:12 ` Mark Brown
[not found] ` <sjdvun1fuj4nyi0bgf268g53.1461086401627@email.android.com>
2016-04-19 17:27 ` Mark Brown
[not found] ` <oe8hqfknrcljrjawnrxlohvr.1461087275186@email.android.com>
2016-04-19 17:54 ` Mark Brown
[not found] ` <us0dopt1inbrt0x47njgc2vy.1461089085965@email.android.com>
2016-04-19 18:46 ` Mark Brown
2016-04-21 11:07 ` Reizer, Eyal
2016-04-21 11:11 ` Mark Brown
2016-04-19 17:07 ` Mark Brown
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=8665E2433BC68541A24DFFCA87B70F5B360C0C5D@DFRE01.ent.ti.com \
--to=eyalr@ti.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=eyalreizer@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®