[<prev] [next>] [day] [month] [year] [list]
Message-ID: <A3BF01DB4A606149A4C20C4C4C808F6C3189E576C2@SAFEX1MAIL1.st.com>
Date: Wed, 8 May 2013 18:10:48 +0200
From: Stephen GALLIMORE <stephen.gallimore@...com>
To: Greg KH <gregkh@...uxfoundation.org>, Arnd Bergmann <arnd@...db.de>
Cc: Srinivas KANDAGATLA <srinivas.kandagatla@...com>,
Stuart MENEFY <stuart.menefy@...com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>
Subject: RE: [RFC 1/8] serial:st-asc: Add ST ASC driver.
>On Wed, May 08, 2013 at 04:34:43PM +0200, Arnd Bergmann wrote:
> > > +#define ASC_MAJOR 204
> > > +#define ASC_MINOR_START 40
> >
> > I don't know what the current policy is on allocating major/minor
> > numbers, but I'm sure you cannot just reuse one that is already used.
First, our apologies, this issue was raised internally and then got forgotten about, there's always something I guess.
> >I agree, why are you trying to create a new tty device name? Can't you use the existing ttyS name and minor number as you will not have any other type of serial
> >device on this system?
That is an interesting question Greg; I believe it probably stems from historic ST SoCs that had two different types of serial devices, something that is no longer the case. We will review our approach to this again, although we are not sure we can use the existing ttyS major/minor (even if that is an acceptable thing to do) because of the (remote) possibility of someone using a standard PCIe attached serial card.
Regards,
-stephen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists