mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David Härdeman" <david@hardeman.nu>
Cc: linux-kernel@vger.kernel.org, jesse.barnes@intel.com
Subject: Re: [RFC/PATCH] Winbond CIR driver for the WPCD376I chip (ACPI/PNP id WEC1022)
Date: Thu, 25 Jun 2009 13:49:46 +0100	[thread overview]
Message-ID: <20090625134946.46109bac@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <55ca74318001aae803805a7bccfaca36.squirrel@www.hardeman.nu>

> How would it work in conjunction with ACPI? When I looked at the ACPI
> dumps for my motherboard, the AML code seemed happy to fiddle with global
> SuperI/O registers (protected using an internal mutex).

If the device is ACPI managed in this way then all accesses to all devices
at that address must go via ACPI as I understand it.

> Also, I don't think it's very user-friendly to have a IR device show up as
> /dev/tty...how would userspace be able to find out that it's actually an
> IR transceiver?

Thats easy to fix - the question is more "is it an 8250 UART with some
quirks" or is it best driven by another device.

You can certainly stop the serial layer grabbing it (or undo that)
providing the port isn't the console (which in this case would make no
sense).

> Therefore I still think it's better to model the driver as an input
> device, and ultimately to teach the input subsystem some specifics of CIR
> devices, similar to how force-feedback devices are handled today.

Seems reasonable for this device.

Alan

  reply	other threads:[~2009-06-25 12:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 21:36 David Härdeman
2009-06-24 22:13 ` Jesse Barnes
2009-06-25 11:46   ` David Härdeman
2009-06-25 16:20     ` Jesse Barnes
2009-06-24 22:45 ` Alan Cox
2009-06-25 12:28   ` David Härdeman
2009-06-25 12:49     ` Alan Cox [this message]
2009-06-25 13:14       ` David Härdeman
2009-06-25 13:17         ` Alan Cox
2009-06-25 13:28           ` David Härdeman
2009-06-25 13:35             ` Alan Cox
2009-10-06  7:32               ` Sean Young

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=20090625134946.46109bac@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=david@hardeman.nu \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®