public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Scott Yuan <scottzero0@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: serial device file is out of order
Date: Mon, 25 Aug 2014 21:19:02 -0700	[thread overview]
Message-ID: <20140826041902.GA27596@kroah.com> (raw)
In-Reply-To: <1409022297-15555-1-git-send-email-scottzero0@gmail.com>

On Tue, Aug 26, 2014 at 11:04:57AM +0800, Scott Yuan wrote:
> On x86 architecture, the configuration of serial device maybe get from ACPI
> DSDT, but the order of DSDT is not mandatory, result as array serial8250_ports
> is out of order. This situation is more obvious in multiple serial port
> mainboard. Sort it by unique id that in DSDT will fix it.

Who cares about the order, you should use the "persistant" names in
/dev/serial/ to connect to things that you really care about which is
which.

> 
> Signed-off-by: Scott Yuan <scottzero0@gmail.com>
> ---
>  drivers/pnp/pnpacpi/core.c          |  1 +
>  drivers/tty/serial/8250/8250_core.c | 40 ++++++++++++++++++++++++++++++++++++-
>  drivers/tty/serial/8250/8250_pnp.c  | 12 +++++++++++
>  include/linux/pnp.h                 |  1 +
>  include/linux/serial_8250.h         |  2 ++
>  5 files changed, 55 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/pnp/pnpacpi/core.c b/drivers/pnp/pnpacpi/core.c
> index a5c6cb7..84b518e 100644
> --- a/drivers/pnp/pnpacpi/core.c
> +++ b/drivers/pnp/pnpacpi/core.c
> @@ -254,6 +254,7 @@ static int __init pnpacpi_add_device(struct acpi_device *device)
>  		return -ENOMEM;
>  
>  	dev->data = device;
> +	dev->is_acpi = 1;
>  	/* .enabled means the device can decode the resources */
>  	dev->active = device->status.enabled;
>  	if (acpi_has_method(device->handle, "_SRS"))
> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> index 7a91c6d..0e5ece5 100644
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -3221,6 +3221,41 @@ static struct uart_8250_port *serial8250_find_match_or_unused(struct uart_port *
>  	return NULL;
>  }
>  
> +static struct uart_8250_port *
> +serial8250_find_match_sorted_port(struct uart_port *port)
> +{
> +	int i, j;
> +	struct uart_8250_port *uart;
> +
> +	uart = container_of(port, struct uart_8250_port, port);
> +
> +	/*
> +	 * We need sorted array serial8250_ports, it is sort by ACPI
> +	 * device unique id, so find an apropriate position to insert.
> +	 */
> +	for (i = 0; i < nr_uarts; i++) {
> +		if (serial8250_ports[i].uid == 0 ||
> +			uart->uid < serial8250_ports[i].uid)
> +			break;
> +	}
> +
> +	/*
> +	 * If current uid that in serial8250_ports is big than port uid,
> +	 * then move 8250 port data.
> +	 */
> +	if (i < nr_uarts - 1 &&
> +		uart->uid < serial8250_ports[i].uid) {
> +		memmove(&serial8250_ports[i+1], &serial8250_ports[i],
> +			(nr_uarts - i - 1) * sizeof(struct uart_8250_port));

Heh, no, that's crazy...

> +
> +		/* modify port.line, since data moved */
> +		for (j = i + 1; j < nr_uarts; j++)
> +			serial8250_ports[j].port.line += 1;
> +	}
> +	serial8250_ports[i].uid = uart->uid;
> +	return &serial8250_ports[i];
> +}

I really don't understand what you are trying to "solve" here.  What is
wrong with the current kernel code?  What does this patch change?

Why is acpi "special"?

greg k-h

  reply	other threads:[~2014-08-26  4:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  3:04 [PATCH] 8250: serial device file is out of order Scott Yuan
2014-08-26  4:19 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-25 11:38 Scott Yuan
2014-08-25 12:18 ` Peter Hurley
2014-08-25 14:46 ` Greg KH

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=20140826041902.GA27596@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=scottzero0@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