public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Secure Digital Host Controller PCI class
Date: Tue, 22 Nov 2005 07:07:18 +0100	[thread overview]
Message-ID: <4382B596.5080001@drzeus.cx> (raw)
In-Reply-To: <20051121214733.GA17793@suse.de>

Greg KH wrote:

>On Mon, Nov 21, 2005 at 12:45:40PM +0100, Pierre Ossman wrote:
>  
>
>>I'm working on a driver for the Secure Digital Host Controller
>>interface. This is a generic interface, so it uses a PCI class for
>>identification instead of vendor/device ids.
>>
>>The class ID used is 0805 and the programming interface (correct term?)
>>indicates DMA capabilities. Greg, since you're the PCI maintainer,
>>perhaps you have the possibility of checking this ID?
>>    
>>
>
>What do you mean "checking this ID"?  Checking it with what?
>
>  
>

I figured you might have access to the official allocations from the PCI
SIG.

>>The standard also dictates a register at offset 0x40 in PCI space. This
>>is a one byte register detailing the number of slots on the controller
>>and the first BAR to use.
>>    
>>
>
>Do you have a pointer to the standard?
>
>  
>

The SDHC standard itself is a well guarded secret. We're basing this
work on the little information that is out there and reverse engineering
the Windows driver. The PCI registers are described in a spec. by Texas
Instruments though:

http://www-s.ti.com/sc/ds/pci6411.pdf

They only use three bits for each field (since their controller only has
three slots), but the Windows driver reads four so that is what I've put
in the patch.

Rgds
Pierre


  reply	other threads:[~2005-11-22  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 11:45 [RFC] Secure Digital Host Controller PCI class Pierre Ossman
2005-11-21 21:47 ` Greg KH
2005-11-22  6:07   ` Pierre Ossman [this message]
2005-11-22  6:39     ` Greg KH
2005-11-22  9:04       ` Pierre Ossman
2005-11-30  8:25         ` Pierre Ossman
2005-12-17 13:00           ` Pierre Ossman

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=4382B596.5080001@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@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