Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Eric Miao <eric.y.miao@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] Palm interrupt driven touchscreen driver
Date: Fri, 05 Jun 2009 12:05:11 +0200	[thread overview]
Message-ID: <s5h63fb573c.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090605093001.GA21128@rakim.wolfsonmicro.main>

At Fri, 5 Jun 2009 10:30:02 +0100,
Mark Brown wrote:
> 
> On Fri, Jun 05, 2009 at 11:16:12AM +0200, Takashi Iwai wrote:
> 
> > I couldn't find it.  But IIRC, the original patch was to add "int irq"
> > field to struct snd_ac97.  I would accept it because it can do any
> > harm.
> 
> Ah, yes - I do remember that proposal.  The problem with that is that it
> doesn't scale up to all the platform data you might want to pass in.
> The WM97xx battery and touchscreen drivers are the main things I'm
> interested in here - the platform data for the WM97xx touch driver is
> struct wm97xx_mach_ops in include/linux/wm97xx.h for example.
> 
> > But, adding a generic "void *driver_data" instead of "int irq" can
> > play a bad game.  It can be dangerous when the creator and the user of
> > this pointer are different drivers.  That was my argument.
> 
> There is potential risk involved in these interfaces but it's the
> standard idiom for doing this on embedded systems.  The buses definitely
> don't want to know anything about the random data that drivers may need
> and since you're not dealing with pluggable or variable hardware in the
> same way as you do on PCs the risks of mismatched data aren't such a big
> deal - you'd generally only be able to encounter problems if you're
> building your own kernel.

Well, but you know that can be broken :)

BTW, can't it be simply driver_data/platform_data of ac97.dev...?


Takashi

  reply	other threads:[~2009-06-05 10:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 21:41 [PATCH] Palm interrupt driven touchscreen driver Marek Vasut
2009-06-04  1:35 ` Eric Miao
2009-06-04  7:20   ` Ian Molton
2009-06-04  8:54   ` Mark Brown
2009-06-04  9:09     ` Jaroslav Kysela
2009-06-04  9:37       ` Mark Brown
2009-06-04  9:44         ` Takashi Iwai
2009-06-04 10:38           ` Mark Brown
2009-06-05  9:16             ` Takashi Iwai
2009-06-05  9:30               ` Mark Brown
2009-06-05 10:05                 ` Takashi Iwai [this message]
2009-06-05 10:20                   ` Mark Brown
2009-06-05 10:38                     ` Takashi Iwai
2009-06-05 10:42                       ` Mark Brown
2009-06-04  9:13     ` Russell King - ARM Linux
2009-06-04  9:27       ` Mark Brown
2009-06-04  8:14 ` Russell King - ARM Linux
2009-06-04 20:05   ` Marek Vasut

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=s5h63fb573c.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux@arm.linux.org.uk \
    --cc=marek.vasut@gmail.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