From: <Tharunkumar.Pasumarthi@microchip.com>
To: <andy.shevchenko@gmail.com>, <Kumaravel.Thiagarajan@microchip.com>
Cc: <linux-serial@vger.kernel.org>, <etremblay@distech-controls.com>,
<gregkh@linuxfoundation.org>, <ilpo.jarvinen@linux.intel.com>,
<wander@redhat.com>, <u.kleine-koenig@pengutronix.de>,
<jk@ozlabs.org>, <macro@orcam.me.uk>, <jirislaby@kernel.org>,
<johan@kernel.org>, <phil.edworthy@renesas.com>,
<geert+renesas@glider.be>, <linux-kernel@vger.kernel.org>,
<lukas@wunner.de>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v2 tty-next 1/3] 8250: microchip: pci1xxxx: Add driver for quad-uart support.
Date: Wed, 26 Oct 2022 10:54:18 +0000 [thread overview]
Message-ID: <cc7d8655cb350b45d547abded44ce839cfe00023.camel@microchip.com> (raw)
In-Reply-To: <CAHp75VfoWii5Eo4n=-JcqE4VZMRoq77jjdTMGfwBF+vzKBXPog@mail.gmail.com>
On Mon, 2022-10-03 at 12:22 +0300, Andy Shevchenko wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
> > + return 0;
> > +}
>
> Do you really have cards that are providing IO ports? If not, simplify
> this accordingly.
Device does not have IO ports. I will remove support in code.
> > + if (num_vectors == 4)
>
> This check should take care of all possible MSI >= 2, correct?
Hardware supports 2 modes:
1. One irq vector for all the instances
2. nth irq vector for nth instance
Some subsystem ID like PCI_SUBDEVICE_ID_MCHP_PCI1XXXX_4p and
PCI_SUBDEVICE_ID_MCHP_PCI11414 will fail in 2nd mode if all the 4 irq vectors
are not assigned. Therefore, to reduce complexity, software will handle only 1
or 4 irq vectors.
> > + for (i = 0; i < nr_ports; i++) {
> > + if (num_vectors == 4)
>
> Ditto.
Hardware supports 2 modes:
1. One irq vector for all the instances
2. nth irq vector for nth instance
Some subsystem ID like PCI_SUBDEVICE_ID_MCHP_PCI1XXXX_4p and
PCI_SUBDEVICE_ID_MCHP_PCI11414 will fail in 2nd mode if all the 4 irq vectors
are not assigned. Therefore, to reduce complexity, software will handle only 1
or 4 irq vectors.
> > + .flags = UART_CAP_FIFO,
> > + },
>
> Can you assign this in ->setup() or so instead of adding a new port type?
Okay, I will assign in pci1xxxx_setup API.
Thanks Andy for the review. Going forward, I will be addressing the comments (if
any).
Thanks,
Tharun Kumar P
next prev parent reply other threads:[~2022-10-26 10:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 6:15 [PATCH v2 tty-next 0/3] 8250: microchip: pci1xxxx: Add driver for the pci1xxxx's quad-uart function Kumaravel Thiagarajan
2022-10-01 6:15 ` [PATCH v2 tty-next 1/3] 8250: microchip: pci1xxxx: Add driver for quad-uart support Kumaravel Thiagarajan
2022-10-03 9:18 ` Ilpo Järvinen
2022-10-03 9:22 ` Andy Shevchenko
2022-10-05 9:51 ` Kumaravel.Thiagarajan
2022-10-26 10:54 ` Tharunkumar.Pasumarthi [this message]
2022-10-31 9:24 ` Tharunkumar.Pasumarthi
2022-10-31 14:37 ` Andy Shevchenko
2022-11-01 15:04 ` Tharunkumar.Pasumarthi
2022-11-01 15:17 ` Andy Shevchenko
2022-11-01 17:54 ` Kumaravel.Thiagarajan
2022-10-03 19:36 ` Christophe JAILLET
2022-10-04 9:46 ` Andy Shevchenko
2022-10-26 11:12 ` Tharunkumar.Pasumarthi
2022-10-26 20:10 ` Christophe JAILLET
2022-10-01 6:15 ` [PATCH v2 tty-next 2/3] 8250: microchip: pci1xxxx: Add rs485 support to quad-uart driver Kumaravel Thiagarajan
2022-10-03 9:04 ` Ilpo Järvinen
2022-11-01 14:53 ` Tharunkumar.Pasumarthi
2022-11-01 15:25 ` Ilpo Järvinen
2022-11-01 15:35 ` Andy Shevchenko
2022-11-01 15:49 ` Ilpo Järvinen
2022-11-01 18:10 ` Tharunkumar.Pasumarthi
2022-10-03 9:20 ` Ilpo Järvinen
2022-10-04 17:51 ` Kumaravel.Thiagarajan
2022-10-05 9:43 ` Ilpo Järvinen
2022-10-01 6:15 ` [PATCH v2 tty-next 3/3] 8250: microchip: pci1xxxx: Add power management functions " Kumaravel Thiagarajan
2022-10-03 9:26 ` Andy Shevchenko
2022-10-04 17:20 ` Kumaravel.Thiagarajan
2022-10-26 11:03 ` Tharunkumar.Pasumarthi
2022-10-31 9:41 ` Tharunkumar.Pasumarthi
2022-11-04 10:23 ` Tharunkumar.Pasumarthi
2022-11-04 12:50 ` Andy Shevchenko
2022-10-03 9:51 ` Ilpo Järvinen
2022-10-04 19:01 ` 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=cc7d8655cb350b45d547abded44ce839cfe00023.camel@microchip.com \
--to=tharunkumar.pasumarthi@microchip.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=ilpo.jarvinen@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).