linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Siewior <al+sa@ml.breakpoint.cc>
To: Jaroslav Kysela <perex@perex.cz>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	dtor@mail.ru, Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, linux-input@vger.kernel.org
Subject: Re: [RFC] ucb1400 touchscreen, irq auto probing and	ac97 with its private field
Date: Thu, 24 Apr 2008 17:44:10 +0200	[thread overview]
Message-ID: <20080424154410.GE26452@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <20080424150211.GC22369@sirena.org.uk>

* Mark Brown | 2008-04-24 16:02:12 [+0100]:

>On Thu, Apr 24, 2008 at 03:57:52PM +0100, Mark Brown wrote:
>
>> > - hacking up the ucb1400 [2] (doesn't solve [3] and needs addition code
>> >   to solve [4]).
>
>> [3] is the issue with the WM97xx touchscreen drivers.  That's currently
>> solved by exactly this issue - as far as I can see from the patch you
>
>The second issue should be method.

I don't think that this is the right way in this case:
- this information equals a global variable. You can't have two
  touchscreens without exra hacking.
- if we keep doing this for all drivers (not just ucb1400) they gonna
  look like drivers/usb/host/ehci-hcd.c (look line 998+) once this chip
  spreads across buses.

Sebatian

  reply	other threads:[~2008-04-24 15:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 14:04 [RFC] ucb1400 touchscreen, irq auto probing and ac97 with its private field Sebastian Siewior
2008-04-24 14:32 ` Jaroslav Kysela
2008-04-24 14:35   ` Sebastian Siewior
2008-04-24 14:57 ` Mark Brown
2008-04-24 15:02   ` [alsa-devel] " Mark Brown
2008-04-24 15:44     ` Sebastian Siewior [this message]
2008-04-24 21:33       ` Mark Brown
2008-04-24 15:35   ` Sebastian Siewior
2008-04-24 20:04     ` Mark Brown
2008-04-24 16:09   ` [alsa-devel] " Takashi Iwai
2008-04-24 18:56     ` Mark Brown
2008-04-25  7:02       ` Takashi Iwai
2008-04-25  7:10         ` [alsa-devel] " Jaroslav Kysela
2008-04-25  7:18           ` Takashi Iwai
2008-04-25  7:35             ` Jaroslav Kysela
2008-04-25  7:46               ` Sebastian Siewior
2008-04-25  7:52               ` Takashi Iwai
2008-04-25  8:23                 ` Jaroslav Kysela
2008-04-25  9:17                   ` Takashi Iwai
2008-04-25  9:45                     ` [alsa-devel] " Jaroslav Kysela
2008-04-25 10:05                       ` Takashi Iwai
2008-04-25 10:18                         ` Jaroslav Kysela
2008-04-25 10:54                   ` Sebastian Siewior
2008-04-25 11:10                     ` Takashi Iwai
2008-04-25 11:22                       ` [alsa-devel] " Jaroslav Kysela
2008-04-25 13:04                         ` Takashi Iwai
2008-04-25 12:49                       ` Sebastian Siewior
2008-04-25 13:01                         ` Takashi Iwai
2008-04-25 15:31               ` Dmitry Torokhov
2008-04-25  9:51         ` Mark Brown
2008-04-25 10:15           ` Takashi Iwai
2008-04-25 10:20             ` Jaroslav Kysela
2008-04-25 10:28             ` [alsa-devel] " Mark Brown

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=20080424154410.GE26452@Chamillionaire.breakpoint.cc \
    --to=al+sa@ml.breakpoint.cc \
    --cc=alsa-devel@alsa-project.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=perex@perex.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).