From: Daniel Mack <daniel@caiaq.de>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Alagu Sankar <alagusankar@embwise.com>,
Volker Ernst <volker.ernst@txtr.com>,
"John W. Linville" <linville@tuxdriver.com>,
Holger Schurig <hs4233@mail.mn-solutions.de>,
Bing Zhao <bzhao@marvell.com>,
libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-mmc@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [PATCH] libertas/sdio: set ECSI and SCSI bits for 1-bit transfers
Date: Tue, 30 Mar 2010 20:40:46 +0200 [thread overview]
Message-ID: <20100330184046.GY30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <1269974259.3019.52.camel@localhost.localdomain>
On Tue, Mar 30, 2010 at 11:37:39AM -0700, Dan Williams wrote:
> On Tue, 2010-03-30 at 19:38 +0200, Daniel Mack wrote:
> > When operating in 1-bit mode, SDAT1 is used as dedicated interrupt line.
> > However, the 8686 will only drive this line when the ECSI and SCSI bits
> > are set in the CCCR_IF register.
>
> While this looks fine enough to me, I don't have enough knowledge of the
> SDIO stack to know whether or not this would be considered a layering
> violation or not. Given that I don't think there's an active maintainer
> for the SDIO subsystem though, I'd say it's fine enough for me...
>
> Any thoughts David since it appears to be at least somewhat SPI related?
I believe that these bits in question are just abused in this case. The
device is not in SPI mode, so according to the specs, the bits shouldn't
make any difference. This makes me think that this is specific to
libertas, and doesn't belong in any lower level.
> Acked-by: Dan Williams <dcbw@redhat.com>
Thanks!
Daniel
next prev parent reply other threads:[~2010-03-30 18:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 17:38 [PATCH] libertas/sdio: set ECSI and SCSI bits for 1-bit transfers Daniel Mack
2010-03-30 18:37 ` Dan Williams
2010-03-30 18:40 ` Daniel Mack [this message]
2010-03-31 8:23 ` Alagu Sankar Vellaichamy
2010-03-31 13:34 ` Daniel Mack
2010-03-31 9:07 ` Michał Mirosław
[not found] ` <x2ve2d7436a1003310207t16a7d1d6r7853de2dfa647c6c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-31 9:08 ` Daniel Mack
2010-03-31 9:49 ` Michał Mirosław
2010-03-31 13:08 ` Daniel Mack
2010-03-31 13:31 ` [PATCH] libertas/sdio: set ECSI bit " Daniel Mack
2010-04-06 2:42 ` Dan Williams
2010-04-06 8:52 ` [PATCH] libertas/sdio: 8686: " Daniel Mack
2010-04-06 16:07 ` Dan Williams
2010-04-13 10:29 ` Daniel Mack
2010-04-13 13:06 ` John W. Linville
2010-04-13 13:21 ` Daniel Mack
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=20100330184046.GY30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alagusankar@embwise.com \
--cc=bzhao@marvell.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=volker.ernst@txtr.com \
/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).