From: Greg KH <greg@kroah.com>
To: John Linn <John.Linn@xilinx.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty/serial: add support for Xilinx PS UART
Date: Tue, 19 Apr 2011 16:21:41 -0700 [thread overview]
Message-ID: <20110419232141.GA27491@kroah.com> (raw)
In-Reply-To: <8d05c32c-9ff1-4eda-9563-6857ede6541a@VA3EHSMHS020.ehs.local>
On Tue, Apr 19, 2011 at 04:22:00PM -0600, John Linn wrote:
> > -----Original Message-----
> > From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> > Sent: Tuesday, April 19, 2011 3:16 PM
> > To: John Linn
> > Cc: linux-kernel@vger.kernel.org; linux-serial@vger.kernel.org
> > Subject: Re: [PATCH] tty/serial: add support for Xilinx PS UART
> >
> > On Tue, 19 Apr 2011 14:14:52 -0600
> > John Linn <john.linn@xilinx.com> wrote:
> >
> > > The Xilinx PS Uart is used on the new ARM based SoC. This
> > > UART is not compatible with others such that a seperate
> > > driver is required.
> >
> > Joyous. I wish people would standardise.
> >
> > > + 213 = /dev/ttyPS0 Xilinx PS serial port 0
> > > + 214 = /dev/ttyPS1 Xilinx PS serial port 1
> > > + 215 = /dev/ttyPS2 Xilinx PS serial port 2
> > > + 216 = /dev/ttyPS3 Xilinx PS serial port 3
> >
> > Is there a specific reason you need fixed minor numbers ? If not
> please
> > use a dynamic range and keep Linus happy.
>
> Hi Alan,
>
> I hope you don't mind me asking a bit more to better understand. Here's
> my
> concerns (maybe not valid).
>
> It seems like since this is a console it can get hard to debug with
> dynamic
> nodes for this driver.
>
> This driver is for an embedded device where we don't want to require
> udev
> or mdev to assign nodes.
Why not use devtmpfs? There's no need to use udev or mdev at all.
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-19 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 20:14 [PATCH] tty/serial: add support for Xilinx PS UART John Linn
2011-04-19 21:15 ` Alan Cox
2011-04-19 21:51 ` John Linn
2011-04-20 9:25 ` Alan Cox
2011-04-20 13:43 ` John Linn
2011-04-19 22:22 ` John Linn
2011-04-19 23:21 ` Greg KH [this message]
2011-04-19 23:39 ` John Linn
2011-04-19 23:42 ` Greg KH
2011-04-19 23:47 ` John Linn
2011-04-20 9:39 ` Alan Cox
2011-04-20 15:19 ` John Linn
2011-04-20 15:35 ` Alan Cox
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=20110419232141.GA27491@kroah.com \
--to=greg@kroah.com \
--cc=John.Linn@xilinx.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox