Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: custom serial driver node not created
Date: Wed, 18 May 2022 13:59:30 +0200	[thread overview]
Message-ID: <YoTfou30lNY3tW6l@kroah.com> (raw)
In-Reply-To: <CAAfyv36U1A21pOOnrUyZ6tKm087dAbJ5kjpOQj6L8kHYBZGmvg@mail.gmail.com>

On Wed, May 18, 2022 at 01:41:18PM +0200, Belisko Marek wrote:
> Hello,
> 
> I'm writing serial tty driver (it's SPI/UART converter) and I get
> inspired by this driver:
> https://github.com/raspberrypi/linux/blob/rpi-5.15.y/drivers/tty/serial/sc16is7xx.c
> 
> I have driver probed and also added port to driver which I see in console:
> [ 2616.826105] spi0.0: ttyTX0 at I/O 0x1 (irq = 0, base_baud = 9375)
> is a test_driver
> 
> so I should see it in /dev/ttyTX0 but it seems node is not created.
> Udev is running on a platform.
> Any ideas what can cause this?

Without seeing the code itself, it's almost impossible to guess.

Also note that udev does not create device nodes (hasn't for over a
decade).  devtmpfs in the kernel does that, udev just helps with
managing the permissions of created nodes if needed.

And why did you pick the ttyTX name?  That's already reserved for that
driver, you should use a new one, right?

And what hardware are you writing this driver for that we don't already
have a driver for it?

thanks,

greg k-h

  reply	other threads:[~2022-05-18 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 11:41 custom serial driver node not created Belisko Marek
2022-05-18 11:59 ` Greg KH [this message]
2022-05-18 12:24   ` Belisko Marek
2022-05-18 12:42     ` Greg KH
2022-05-18 12:47       ` Belisko Marek

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=YoTfou30lNY3tW6l@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=marek.belisko@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