mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kumaravel.Thiagarajan@microchip.com
Cc: andy.shevchenko@gmail.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	u.kleine-koenig@pengutronix.de, johan@kernel.org,
	wander@redhat.com, etremblay@distech-controls.com,
	macro@orcam.me.uk, geert+renesas@glider.be, jk@ozlabs.org,
	phil.edworthy@renesas.com, Lukas Wunner <lukas@wunner.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-serial <linux-serial@vger.kernel.org>,
	UNGLinuxDriver@microchip.com
Subject: RE: [PATCH v1 tty-next 1/2] 8250: microchip: pci1xxxx: Add driver for the quad-uart function in the multi-function endpoint of pci1xxxx device.
Date: Thu, 1 Sep 2022 16:41:48 +0300 (EEST)	[thread overview]
Message-ID: <63f48d1-f716-5040-c8d1-486087bd1c5e@linux.intel.com> (raw)
In-Reply-To: <BN8PR11MB3668BAC07D493EE02AEAEB14E97B9@BN8PR11MB3668.namprd11.prod.outlook.com>

On Thu, 1 Sep 2022, Kumaravel.Thiagarajan@microchip.com wrote:

> > > +       const unsigned int standard_baud_list[] = {50, 75, 110, 134, 150, 300,
> > > +                                               600, 1200, 1800, 2000, 2400, 3600,
> > > +                                               4800, 7200, 9600, 19200, 38400, 57600,
> > > +                                               115200, 125000, 136400, 150000, 166700,
> > > +                                               187500, 214300, 250000, 300000, 375000,
> > > +                                               500000, 750000,
> > > + 1000000, 1500000};
> > 
> > Why?!
>
> The standard baud rates are handled within serial8250_do_set_termios 
> which is invoked from within mchp_pci1xxxx_set_termios in first place. 
> Hence if it matches with any of the standard baudrates,
> it can return immediately.

Care to explain why the baudrates in your table don't match those in 
tty_baudrate.c? ...It makes no sense to me that you call these "standard 
baud rates".


-- 
 i.


  reply	other threads:[~2022-09-01 13:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 18:00 [PATCH v1 tty-next 0/2] 8250: microchip: pci1xxxx: Add driver for the pci1xxxx's quad-uart function Kumaravel Thiagarajan
2022-08-30 18:00 ` [PATCH v1 tty-next 1/2] 8250: microchip: pci1xxxx: Add driver for the quad-uart function in the multi-function endpoint of pci1xxxx device Kumaravel Thiagarajan
2022-08-30 19:53   ` Andy Shevchenko
2022-09-01 13:33     ` Kumaravel.Thiagarajan
2022-09-01 13:41       ` Ilpo Järvinen [this message]
2022-09-02 11:57         ` Kumaravel.Thiagarajan
2022-09-02 15:02           ` Andy Shevchenko
2022-09-05 12:01             ` Kumaravel.Thiagarajan
2022-08-30 19:58   ` Geert Uytterhoeven
2022-09-01 14:09     ` Kumaravel.Thiagarajan
2022-08-30 22:18   ` kernel test robot
2022-08-30 22:29   ` kernel test robot
2022-08-31  9:42   ` Ilpo Järvinen
2022-09-01 14:21     ` Kumaravel.Thiagarajan
2022-08-30 18:00 ` [PATCH v1 tty-next 2/2] 8250: microchip: pci1xxxx: Add power management functions to pci1xxxx's quad-uart driver Kumaravel Thiagarajan
2022-08-30 19:56   ` Andy Shevchenko
2022-09-01 13:49     ` Kumaravel.Thiagarajan
2022-09-29  9:34       ` Kumaravel.Thiagarajan
2022-08-30 23:00   ` kernel test robot
2022-08-31  9:53   ` Ilpo Järvinen
2022-09-02  2:20     ` Kumaravel.Thiagarajan

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=63f48d1-f716-5040-c8d1-486087bd1c5e@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Kumaravel.Thiagarajan@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=etremblay@distech-controls.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=jk@ozlabs.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=macro@orcam.me.uk \
    --cc=phil.edworthy@renesas.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wander@redhat.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

all inboxes | Powered by JetHome®