All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Ingo Oeser <ioe-lkml@rameria.de>,
	linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
	Greg KH <gregkh@suse.de>,
	ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: [ALSA STABLE 3/3] a few more -- unregister platform device again if probe was unsuccessful
Date: Thu, 13 Apr 2006 15:57:57 +0100	[thread overview]
Message-ID: <20060413145756.GA29959@flint.arm.linux.org.uk> (raw)
In-Reply-To: <443E5AAD.5040800@keyaccess.nl>

On Thu, Apr 13, 2006 at 04:05:33PM +0200, Rene Herman wrote:
> Not honouring/passing up probe() method error returns, not even -ENODEV, 
> makes some sense for discoverable busses such as PCI where you at least 
> have a driver independent bus_id sitting in /sys/devices/pci* that you 
> can later echo into /sys/bus/pci/drivers/*/bind to make the driver bind 
> to a device, but not much sense for the platform bus. Platform devices 
> only "exist" (in /sys/devices/platform) due to the driver creating them 
> itself and keeping them after failing a probe means that directory 
> becomes an enumeration of the drivers we loaded, rather than a view of 
> what's present in the system.

Incorrect.  In some circumstances, they may be created by architecture
support code, and might be created and destroyed dynamically by
architecture support code.

> The driver model crowd did not seem exceedingly interested in the 
> problem though:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114417829014332&w=2

Incorrect summary.  The ALSA use model of the driver model doesn't fit
with the driver model use model.  It's not that we're not interested
in it - it's that it's perverted to the way driver model folk intend
the subsystem to work, and the way that platform devices are used on
some architectures.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-04-13 14:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13  1:46 [ALSA STABLE 3/3] a few more -- unregister platform device again if probe was unsuccessful Rene Herman
2006-04-13  9:26 ` Ingo Oeser
2006-04-13  9:31   ` Russell King
2006-04-13 14:05   ` Rene Herman
2006-04-13 14:05   ` Rene Herman
2006-04-13 14:57     ` Russell King [this message]
2006-04-13 16:17       ` Rene Herman
2006-04-13 16:17       ` Rene Herman
2006-04-13 17:05         ` Russell King
2006-04-13 17:05         ` Russell King
2006-04-13 18:47           ` Rene Herman
2006-04-13 18:47             ` Rene Herman
2006-04-13 22:02           ` Greg KH
2006-04-13 22:02           ` Greg KH
2006-04-13 23:12             ` Rene Herman
2006-04-13 23:12               ` Rene Herman
2006-04-15 13:16               ` Takashi Iwai
2006-04-15 13:16                 ` Takashi Iwai
2006-04-13 14:57     ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13  1:46 Rene Herman

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=20060413145756.GA29959@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@suse.de \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    --cc=tiwai@suse.de \
    /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.