From: Mark Brown <broonie@kernel.org>
To: "Reizer, Eyal" <eyalr@ti.com>
Cc: "kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"���� �����" <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 18:27:06 +0100 [thread overview]
Message-ID: <20160419172706.GD3217@sirena.org.uk> (raw)
In-Reply-To: <sjdvun1fuj4nyi0bgf268g53.1461086401627@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On Tue, Apr 19, 2016 at 05:21:01PM +0000, Reizer, Eyal wrote:
> The main quirk here is that i need to send extra clocks after the spi init command while the CS pin is "high" in order to put the wilink chip into SPI mode.
> So just sending an empty transfer wouldnt do the trick here.
A single byte transfer would result in extra clocks being sent so there
must be more to it than that...
> Do you have a recomendation on how to do it without changing the core logic. If it is possible it would be really great.
Please be explicit about what you're trying to do here. I imagine you
may need to change the core logic but we need to know what it is that
the device needs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-19 17:27 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 ` [PATCHv2] wlcore: spi: add wl18xx support 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
2016-04-19 17:12 ` Mark Brown
[not found] ` <sjdvun1fuj4nyi0bgf268g53.1461086401627@email.android.com>
2016-04-19 17:27 ` Mark Brown [this message]
[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=20160419172706.GD3217@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eyalr@ti.com \
--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