From: Russell King <rmk@arm.linux.org.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: torvalds@transmeta.com, dahinds@users.sourceforge.net,
davej@suse.de, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org,
pcmcia-cs-devel@lists.sourceforge.net,
linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH 2.5.61] pcmcia: add device_class pcmcia_socket, update devices & drivers
Date: Sat, 15 Feb 2003 13:12:13 +0000 [thread overview]
Message-ID: <20030215131213.A26902@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030215123308.GA1073@brodo.de>; from linux@brodo.de on Sat, Feb 15, 2003 at 01:33:09PM +0100
On Sat, Feb 15, 2003 at 01:33:09PM +0100, Dominik Brodowski wrote:
> A new device_class "pcmcia_socket_class" is introduced for PCMCIA and
> CardBus sockets. All socket drivers I could find are updated so that they
> register a driver, and -if necessary- the "platform"/legacy device. This
> will allow for a cleanup of pcmcia_{un}register_socket() /
> {un}register_ss_entry() as well as reflect the parent for pcmcia_bus
> devices.
> +
> +static struct platform_device sa1100_pcmcia_device = {
> + .name = "sa1100_pcmcia",
> + .id = 0,
> + .dev = {
> + .name = "sa1100_pcmcia",
> + },
> +};
> +
This probably isn't the best way to handle this - the sa1100 device driver
is actually a generic driver to couple to GPIO-based PCMCIA implementations,
which includes the sa1111 stuff. The sa1111 stuff itself registers with
sysfs.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2003-02-15 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 12:33 [PATCH 2.5.61] pcmcia: add device_class pcmcia_socket, update devices & drivers Dominik Brodowski
2003-02-15 13:12 ` Russell King [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=20030215131213.A26902@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dahinds@users.sourceforge.net \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@brodo.de \
--cc=pcmcia-cs-devel@lists.sourceforge.net \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.