public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org,
	jgarzik@pobox.com
Subject: Re: [PATCH 1/2] [PCI] Secure Digital Host Controller id and regs
Date: Sun, 12 Feb 2006 18:28:47 +0300	[thread overview]
Message-ID: <20060212182847.375d7907.vsu@altlinux.ru> (raw)
In-Reply-To: <20060211001523.10315.34499.stgit@poseidon.drzeus.cx>

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]

On Sat, 11 Feb 2006 01:15:23 +0100 Pierre Ossman wrote:

> Class code and register definitions for the Secure Digital Host Controller
> standard.
> 
> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
> ---
> 
>  include/linux/pci_ids.h  |    1 +
>  include/linux/pci_regs.h |    3 +++
>  2 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index 7a61ccd..5fa8ebe 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -69,6 +69,7 @@
>  #define PCI_CLASS_SYSTEM_TIMER		0x0802
>  #define PCI_CLASS_SYSTEM_RTC		0x0803
>  #define PCI_CLASS_SYSTEM_PCI_HOTPLUG	0x0804
> +#define PCI_CLASS_SYSTEM_SDHCI		0x0805
>  #define PCI_CLASS_SYSTEM_OTHER		0x0880
>  
>  #define PCI_BASE_CLASS_INPUT		0x09
> diff --git a/include/linux/pci_regs.h b/include/linux/pci_regs.h
> index d27a78b..e6deda5 100644
> --- a/include/linux/pci_regs.h
> +++ b/include/linux/pci_regs.h
> @@ -108,6 +108,9 @@
>  #define PCI_INTERRUPT_PIN	0x3d	/* 8 bits */
>  #define PCI_MIN_GNT		0x3e	/* 8 bits */
>  #define PCI_MAX_LAT		0x3f	/* 8 bits */
> +#define PCI_SLOT_INFO		0x40	/* 8 bits */
> +#define  PCI_SLOT_INFO_SLOTS(x)		((x >> 4) & 7)
> +#define  PCI_SLOT_INFO_FIRST_BAR_MASK	0x07

Does this really belong here?  This register is specific to the SDHCI
class, while all other definitions in pci_regs.h apply to all PCI
devices.

drivers/mmc/sdhci.h seems to be a more logical place for SLOT_INFO
definitions.

>  
>  /* Header type 1 (PCI-to-PCI bridges) */
>  #define PCI_PRIMARY_BUS		0x18	/* Primary bus number */
> 

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2006-02-12 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  0:15 [PATCH 1/2] [PCI] Secure Digital Host Controller id and regs Pierre Ossman
2006-02-11  0:15 ` [PATCH 2/2] [MMC] Secure Digital Host Controller Interface driver Pierre Ossman
2006-02-12 10:01   ` Andrew Morton
2006-02-12 10:20     ` Pierre Ossman
2006-02-12 17:14   ` Sergey Vlasov
2006-02-12 17:24     ` Pierre Ossman
2006-02-18 22:08     ` Pierre Ossman
2006-02-12 15:28 ` Sergey Vlasov [this message]
2006-02-12 15:36   ` [PATCH 1/2] [PCI] Secure Digital Host Controller id and regs Pierre Ossman
2006-02-18 22:07   ` 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=20060212182847.375d7907.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --cc=drzeus@drzeus.cx \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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