From: Kalle Valo <kvalo@codeaurora.org>
To: "Reizer\, Eyal" <eyalr@ti.com>
Cc: "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>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4] wlcore: spi: add wl18xx support
Date: Fri, 08 Jul 2016 12:57:51 +0300 [thread overview]
Message-ID: <87bn281mg0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8665E2433BC68541A24DFFCA87B70F5B3613BF60@DFRE01.ent.ti.com> (Eyal Reizer's message of "Sun, 26 Jun 2016 10:10:54 +0000")
"Reizer, Eyal" <eyalr@ti.com> writes:
> Add support for using with both wl12xx and wl18xx.
>
> - all wilink family needs special init command for entering wspi mode.
> extra clock cycles should be sent after the spi init command while the
> cs pin is high.
> - Use inverted chip select for sending a dummy 4 bytes command that
> completes the init stage.
>
> Signed-off-by: Eyal Reizer <eyalr@ti.com>
> ---
> v1->v2:update device tree bindings configuration
> v2->v3:revert from manual gpio manipulation. use inverted chip select instead
> for sending the extra init cycle which, achieves the same hardware purpose.
> update device tree bindings docucmentation accordingly
> v3->v4: Remove redundant data form binding documentation and fix chip select
> number mismatch in wl1271 example
Doesn't apply to wireless-drivers-next, please resend.
Applying: wlcore: spi: add wl18xx support
Using index info to reconstruct a base tree...
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/wireless/ti/wlcore/spi.c
CONFLICT (content): Merge conflict in drivers/net/wireless/ti/wlcore/spi.c
Failed to merge in the changes.
Patch failed at 0001 wlcore: spi: add wl18xx support
--
Kalle Valo
prev parent reply other threads:[~2016-07-08 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466935675-14696-1-git-send-email-eyalr@ti.com>
[not found] ` <1466935675-14696-1-git-send-email-eyalr-l0cyMroinI0@public.gmane.org>
2016-06-26 10:10 ` [PATCH v4] wlcore: spi: add wl18xx support Reizer, Eyal
2016-06-28 20:56 ` Rob Herring
2016-07-08 9:57 ` Kalle Valo [this message]
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=87bn281mg0.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=eyalr@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).