From: Flavio Suligoi <f.suligoi@asem.it>
To: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: R: R: R: R: [PATCH v1] serial: 8250_fintek: Print Fintek chip name
Date: Wed, 16 Dec 2020 09:44:08 +0000 [thread overview]
Message-ID: <44e270c8097c4351a92885fc21793f8d@asem.it> (raw)
In-Reply-To: <47f3c665-df17-27ca-7835-5917f70a9665@gmail.com>
Hi Peter,
> >>>
> >>> dmesg| grep ttyS
> >>
> >> But as they work the same, why does it matter?
> >
> > Yes you are right, by the user point of view, they are the same.
> >
> >>
> >> Userspace should not care here. Isn't there some other id you can
> >> read/query for a hardware database tool to determine this?
>
>
> As Greg mentions, The userspace don't care what IC they are using.
> We can use Linux RS485 API to control or check the serial port.
>
> https://www.kernel.org/doc/html/latest/driver-api/serial/serial-rs485.html
Yes, right!
Thanks for your info!
>
> --
> With Best Regards,
> Peter Hong
Best regards,
Flavio
prev parent reply other threads:[~2020-12-16 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 13:14 [PATCH v1] serial: 8250_fintek: Print Fintek chip name Flavio Suligoi
2020-12-14 13:42 ` Greg Kroah-Hartman
2020-12-15 0:29 ` Ji-Ze Hong (Peter Hong)
2020-12-15 6:30 ` Jiri Slaby
2020-12-15 13:35 ` R: " Flavio Suligoi
2020-12-15 13:42 ` Greg Kroah-Hartman
2020-12-15 14:06 ` R: " Flavio Suligoi
2020-12-15 14:38 ` Greg Kroah-Hartman
2020-12-15 15:06 ` R: " Flavio Suligoi
2020-12-16 0:53 ` Ji-Ze Hong (Peter Hong)
2020-12-16 9:44 ` Flavio Suligoi [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=44e270c8097c4351a92885fc21793f8d@asem.it \
--to=f.suligoi@asem.it \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=hpeter@gmail.com \
--cc=jirislaby@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).