linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	gregkh@linuxfoundation.org, jirislaby@kernel.org,
	ilpo.jarvinen@linux.intel.com, macro@orcam.me.uk,
	cang1@live.co.uk, colin.i.king@gmail.com,
	phil.edworthy@renesas.com, biju.das.jz@bp.renesas.com,
	geert+renesas@glider.be, lukas@wunner.de,
	u.kleine-koenig@pengutronix.de, wander@redhat.com,
	etremblay@distech-controls.com, jk@ozlabs.org,
	UNGLinuxDriver@microchip.com,
	Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
Subject: Re: [PATCH v9 tty-next 2/4] serial: 8250_pci1xxxx: Add driver for quad-uart support
Date: Thu, 15 Dec 2022 19:42:32 +0200	[thread overview]
Message-ID: <Y5tciHzsEGU67h1Z@smile.fi.intel.com> (raw)
In-Reply-To: <20221216052656.2098100-3-kumaravel.thiagarajan@microchip.com>

On Fri, Dec 16, 2022 at 10:56:54AM +0530, Kumaravel Thiagarajan wrote:
> pci1xxxx is a PCIe switch with a multi-function endpoint on one of
> its downstream ports. Quad-uart is one of the functions in the
> multi-function endpoint. This driver loads for the quad-uart and
> enumerates single or multiple instances of uart based on the PCIe
> subsystem device ID.

...

> +static const int logical_to_physical_port_idx[][MAX_PORTS] = {
> +	{0,  1,  2,  3},/* PCI12000, PCI11010, PCI11101, PCI11400, PCI11414 */
> +	{0,  1,  2,  3},/* PCI4p */
> +	{0,  1,  2, -1},/* PCI3p012 */
> +	{0,  1,  3, -1},/* PCI3p013 */
> +	{0,  2,  3, -1},/* PCI3p023 */
> +	{1,  2,  3, -1},/* PCI3p123 */
> +	{0,  1, -1, -1},/* PCI2p01 */
> +	{0,  2, -1, -1},/* PCI2p02 */
> +	{0,  3, -1, -1},/* PCI2p03 */
> +	{1,  2, -1, -1},/* PCI2p12 */
> +	{1,  3, -1, -1},/* PCI2p13 */
> +	{2,  3, -1, -1},/* PCI2p23 */
> +	{0, -1, -1, -1},/* PCI1p0 */
> +	{1, -1, -1, -1},/* PCI1p1 */
> +	{2, -1, -1, -1},/* PCI1p2 */
> +	{3, -1, -1, -1},/* PCI1p3 */

One space or TAB before /* will increase readability.

> +};

...

> +	ret = serial8250_pci_setup_port(pdev, port, 0, port_idx * 256, 0);

Actually isn't 0x100 better (show that there is an offset rather than
a value of an register)?

> +	if (ret < 0)
> +		return ret;

...

> +static unsigned int pci1xxxx_get_max_port(int subsys_dev)
> +{
> +	int i = 0;

What the point to assign this one?

Actually, better is

	unsigned int = MAX_PORTS;

> +	if (subsys_dev < ARRAY_SIZE(logical_to_physical_port_idx))

> +		for (i = MAX_PORTS - 1; i >= 0; i--)

while (i--) {

> +			if (logical_to_physical_port_idx[subsys_dev][i] != -1)
> +				return logical_to_physical_port_idx[subsys_dev][i] + 1;

}

(Note missinng {} in the above code. Does checkpatch complain on this?)

> +
> +	if (subsys_dev != PCI_SUBDEVICE_ID_EFAR_PCI11414)
> +		return 1;
> +
> +	return 4;
> +}

...

> +	num_vectors = pci_alloc_irq_vectors(pdev, 1, max_vec_reqd, PCI_IRQ_ALL_TYPES);
> +	if (num_vectors < 0) {

> +		pci_iounmap(pdev, priv->membase);

Here is inconsistency on how you interpret pci_*() calls when
pcim_enable_device() has been used. I.e. for IRQ you don't
deallocate resources explicitly (yes, it's done automatically
anyway), but you explicitly call pci_iounmap(). Choose a single
approach for all of them.

> +		return num_vectors;
> +	}

...

> +static_assert((ARRAY_SIZE(logical_to_physical_port_idx) ==
> +	       PCI_SUBDEVICE_ID_EFAR_PCI1XXXX_1p3 + 1));

Can be still one line.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-12-15 17:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  5:26 [PATCH v9 tty-next 0/4] serial: 8250_pci1xxxx: Add driver for the pci1xxxx's quad-uart function Kumaravel Thiagarajan
2022-12-16  5:26 ` [PATCH v9 tty-next 1/4] serial: 8250_pci: Add serial8250_pci_setup_port definition in 8250_pcilib.c Kumaravel Thiagarajan
2022-12-16  5:26 ` [PATCH v9 tty-next 2/4] serial: 8250_pci1xxxx: Add driver for quad-uart support Kumaravel Thiagarajan
2022-12-15 17:42   ` Andy Shevchenko [this message]
2022-12-15 17:44     ` Andy Shevchenko
2022-12-16  5:40     ` Tharunkumar.Pasumarthi
2022-12-16  8:26       ` Andy Shevchenko
2022-12-16  9:30         ` Tharunkumar.Pasumarthi
2022-12-16  9:38           ` Andy Shevchenko
2022-12-16 10:31             ` Tharunkumar.Pasumarthi
2022-12-16 13:29               ` Andy Shevchenko
2022-12-16  5:26 ` [PATCH v9 tty-next 3/4] serial: 8250_pci1xxxx: Add RS485 support to quad-uart driver Kumaravel Thiagarajan
2022-12-16  5:26 ` [PATCH v9 tty-next 4/4] serial: 8250_pci1xxxx: Add power management functions " 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=Y5tciHzsEGU67h1Z@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cang1@live.co.uk \
    --cc=colin.i.king@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=kumaravel.thiagarajan@microchip.com \
    --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=tharunkumar.pasumarthi@microchip.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).