mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
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 15:14:36 +0200 (CEST)	[thread overview]
Message-ID: <c17c39d3458ffa3aebee03ff26d90c23.squirrel@www.hardeman.nu> (raw)
In-Reply-To: <20090625134946.46109bac@lxorguk.ukuu.org.uk>

On Thu, June 25, 2009 14:49, Alan Cox wrote:
> 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).

Which way of stopping the serial layer from grabbing the port did you have
in mind?

If I call uart_remove_one_port, I'd need to get struct uart_driver *drv
and struct uart_port *port from somewhere. Also, it'd be quite ugly to
have /dev/ttyX appear and magically disappear during boot (since 8250 is
compiled in with most distro kernels and my driver would be a module which
would be loaded much later).

The only alternative I could think of would be to get the serial core to
check with acpi_check_resource_conflict for ports that have not been
discovered via PNP/ACPI?

-- 
David Härdeman


  reply	other threads:[~2009-06-25 13:14 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
2009-06-25 13:14       ` David Härdeman [this message]
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=c17c39d3458ffa3aebee03ff26d90c23.squirrel@www.hardeman.nu \
    --to=david@hardeman.nu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®