mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Clemens Ladisch <clemens@ladisch.de>,
	Takashi Iwai <tiwai@suse.de>, Andreas Mohr <andi@lisas.de>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 1/2] SOUND: kill gameport bits
Date: Mon, 5 Aug 2024 14:29:38 -0700	[thread overview]
Message-ID: <ZrFEQkveaV6Q-Ayf@google.com> (raw)
In-Reply-To: <20140828211110.GA24519@suse.cz>

Hi everyone,

On Thu, Aug 28, 2014 at 11:11:10PM +0200, Vojtech Pavlik wrote:
> On Thu, Aug 28, 2014 at 10:03:55PM +0200, Clemens Ladisch wrote:
> > Takashi Iwai wrote:
> > > did anyone test the patch at all...?
> > 
> > Appears to work.  The ymfpci gameport seems to be somewhat unreliable:
> > 
> >  analog.c: 100 out of 17347 reads (0%) on pci0000:06:06.1/gameport0 failed
> >  analog.c: 122 out of 1111 reads (10%) on pci0000:06:07.0/gameport0 failed
> 
> The analog.c gameport read routine is unreliable by design. 
> 
> The 558 chip is not an ADC, it's an one-shot timer from 1971. The analog
> position of the joystick is measured by timing bit changes on the
> gameport.
> 
> analog.c does that without disabling interrupts, as the read can take
> several milliseconds. analog.c instead detects when an interrupt influenced
> the measurement too much and retries.
> 
> The retries are counted and reported.
> 
> 10% is a largeish number, but still something the analog.c driver can
> cope with and give reliable results. 

So 10 years have passed since I tried to remove gameport support from
the kernel. I do not believe there were a lot of meaningful fixes.

Do we still want to keep this in the kernel or is it time for gameport
to retire?

Thanks.

-- 
Dmitry

  reply	other threads:[~2024-08-05 21:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  2:46 Andreas Mohr
2014-08-20  5:18 ` Dmitry Torokhov
2014-08-20  5:50   ` Andreas Mohr
2014-08-20  6:09   ` Takashi Iwai
2014-08-20  6:31     ` Dmitry Torokhov
2014-08-20  7:05       ` Takashi Iwai
2014-08-20 12:15         ` Takashi Iwai
2014-08-20 14:49           ` Dmitry Torokhov
2014-08-21  7:16             ` Geert Uytterhoeven
2014-08-20 12:29         ` One Thousand Gnomes
2014-08-20 12:53           ` Geert Uytterhoeven
2014-08-21 11:29         ` Takashi Iwai
2014-08-24  5:07           ` Andreas Mohr
2014-08-25  7:13             ` Takashi Iwai
2014-08-28 20:03               ` Clemens Ladisch
2014-08-28 21:11                 ` Vojtech Pavlik
2024-08-05 21:29                   ` Dmitry Torokhov [this message]
2014-08-20 14:27     ` Andreas Mohr
2014-08-20 14:48       ` Dmitry Torokhov
2014-08-20  6:39   ` Vojtech Pavlik
2014-08-20 12:20     ` One Thousand Gnomes
  -- strict thread matches above, loose matches on Subject: below --
2014-08-19 16:41 Dmitry Torokhov
2014-08-20  7:33 ` Clemens Ladisch

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=ZrFEQkveaV6Q-Ayf@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=andi@lisas.de \
    --cc=clemens@ladisch.de \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=vojtech@suse.cz \
    /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

Powered by JetHome