From: Greg KH <gregkh@linuxfoundation.org>
To: Karthik Manamcheri <karthik.manamcheri@ni.com>
Cc: Karthik Manamcheri <karthik.manamcheri@gmail.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: 8250: Make SERIAL8250_CONFIG_RUNTIME_UARTS work correctly
Date: Thu, 28 Mar 2013 15:15:34 -0700 [thread overview]
Message-ID: <20130328221534.GA23191@kroah.com> (raw)
In-Reply-To: <OFCAF9F7AE.C68748CA-ON86257B3C.00771424-86257B3C.00798499@ni.com>
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Mar 28, 2013 at 05:07:18PM -0500, Karthik Manamcheri wrote:
> The config option should have been SERIAL_8250_RUNTIME_UARTS. I mis-typed the
> name of the config option.
>
> Consider a situation where I have an ARM based system and therefore no legacy
> ports. Say, I have two memory-mapped ports. I use device tree to describe the
> ports. What would be the config options I set so that I get only the two ports
> in my system? I do not want legacy ports being created automatically and I want
> it to be flexible enough that it creates the devices based only on the device
> tree. I expected setting SERIAL_8250_RUNTIME_UARTS = 0 to work because the
> description said, "Set this to the maximum number of serial ports you want the
> kernel to register at boot time." Unfortunately, even though
> SERIAL_8250_NR_UARTS was set to a default value of 4, I did not get any device
> nodes (because SERIAL_8250_RUNTIME_UARTS was 0). This is what this patch is
> trying to address.
>
> SERIAL_8250_NR_UARTS controls the maximum number of ports you can support.
> SERIAL_8250_RUNTIME_UARTS specifies the number of ports you want to create
> automatically for legacy ports at boot time. All other ports will be created
> when serial8250_register_port is called (and if does not exceed the total
> number of supported ports as specified by SERIAL_8250_NR_UARTS).
Great, care to put all of that into the changelog section of the patch
and resend it after fixing the config option as well?
thanks,
greg "I have to drag it out of people" k-h
prev parent reply other threads:[~2013-03-28 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 20:20 [PATCH] serial: 8250: Make SERIAL8250_CONFIG_RUNTIME_UARTS work correctly Karthik Manamcheri
2013-03-28 21:22 ` Greg KH
[not found] ` <OFCAF9F7AE.C68748CA-ON86257B3C.00771424-86257B3C.00798499@ni.com>
2013-03-28 22:15 ` Greg KH [this message]
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=20130328221534.GA23191@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=karthik.manamcheri@gmail.com \
--cc=karthik.manamcheri@ni.com \
--cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.