From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
David Brownell
<dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] drivers: spi-gpio: add support for controllers without MISO or MOSI pin
Date: Tue, 1 Jun 2010 08:59:52 -0600 [thread overview]
Message-ID: <AANLkTilQ5yD16LAq4xEmXKAmrNqO8eWFh0BmHPd2cR0q@mail.gmail.com> (raw)
In-Reply-To: <001701cb0180$60f0b320$22d21960$%szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
On Tue, Jun 1, 2010 at 5:48 AM, Marek Szyprowski
<m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> wrote:
> Hello,
>
> On Thursday, April 01, 2010 12:36 PM Marek Szyprowski wrote:
>
>> There are some boards that do not strictly follow SPI standard and use
>> only 3 wires (SCLK, MOSI or MISO, SS) for connecting some simple auxiliary
>> chips and controls them with GPIO based 'spi controller'. In this
>> configuration the MISO or MOSI line is missing (it is not required if the
>> chip does not transfer any data back to host or host only reads data from
>> chip).
>>
>> This patch adds support for such non-standard configuration in GPIO-based
>> SPI controller. It has been tested in configuration without MISO pin.
>>
>> Reviewed-by: Kyungmin Park <kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>> Signed-off-by: Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>
> Is there any progress on merging this patch? It hangs on the patchwork for
> 2 months still marked as 'new'. I'm a bit confused. The idea behind the patch
> was already accepted (see commit 568d0697f42771425ae9f1e9a3db769fef7e10b6)
> but then the patch is still waiting... My fault I didn't asked for it on the
> beginning of the merge window.
I'm not convinced this is the best approach. I did look at it, but
decided not to merge it yet. It adds code to the hottest path in the
spi-gpio driver (not that this driver will ever be fast, but on
bit-banged gpio, every instruction counts).
I was delayed it getting on the SPI backlog this merge cycle due to
travel, so I've deferred making a decision on this patch. I'll be
taking another look in the next few weeks and I'll let you know
whether or not I'll pick it up for 2.6.36
g.
------------------------------------------------------------------------------
next prev parent reply other threads:[~2010-06-01 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 10:35 [PATCH] drivers: spi-gpio: add support for controllers without MISO or MOSI pin Marek Szyprowski
[not found] ` <1270118151-13286-1-git-send-email-m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-04-01 11:17 ` jassi brar
[not found] ` <i2r1b68c6791004010417q1aaa996au22f526afbedb9635-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-01 13:10 ` Marek Szyprowski
2010-06-01 11:48 ` Marek Szyprowski
[not found] ` <001701cb0180$60f0b320$22d21960$%szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-06-01 14:59 ` Grant Likely [this message]
[not found] ` <AANLkTilQ5yD16LAq4xEmXKAmrNqO8eWFh0BmHPd2cR0q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-02 6:00 ` Marek Szyprowski
[not found] ` <002b01cb0218$ddab68e0$99023aa0$%szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-06-02 9:00 ` Jassi Brar
[not found] ` <AANLkTim-yZb55jAyOaQJ_pOnp-LcXh-wdzw4TKqAyfea-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-09 7:14 ` Marek Szyprowski
[not found] ` <000301cb07a3$679c6ec0$36d54c40$%szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-06-16 19:52 ` Grant Likely
[not found] ` <AANLkTimT_IHfv4dKXuvTpa8M4L_MDqIvjrDPBLgzKUWn-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-17 6:54 ` Marek Szyprowski
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=AANLkTilQ5yD16LAq4xEmXKAmrNqO8eWFh0BmHPd2cR0q@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).