public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Matthew Howell <matthew.howell@sealevel.com>
Cc: gregkh@linuxfoundation.org, jeff.baldwin@sealevel.com,
	james.olson@sealevel.com, ryan.wenglarz@sealevel.com,
	darren.beeson@sealevel.com, linux-serial@vger.kernel.org,
	ilpo.jarvinen@linux.intel.com
Subject: Re: [PATCH V4 2/2] serial: exar: Add RS-485 support for Sealevel XR17V35X based cards
Date: Wed, 6 Sep 2023 16:44:28 +0300	[thread overview]
Message-ID: <ZPiCPJYfiR9ZfVJC@smile.fi.intel.com> (raw)
In-Reply-To: <e2564a57-128e-cd9c-9bae-23b155fd8ee9@sealevel.com>

On Tue, Sep 05, 2023 at 12:06:20PM -0400, Matthew Howell wrote:
> From: Matthew Howell <matthew.howell@sealevel.com

Okay, I started reviewing it and it has all the same issues that I pointed
out previously. Are you sure you sent a _new_ version?

For your convenience I left all comments here.

> 
> Sealevel XR1735X based cards utilize DTR to control RS-485 Enable, but the 
> current implementation of 8250_exar uses RTS for the auto-RS485-Enable 
> mode of the XR17V35X UARTs. This patch implements DTR Auto-RS485 on 

All four above and two below (Link: and supposed to be a blank line)
have a trailing space. Which editor do you use? You probably need to configure
it to avoid this.

> Sealevel cards.

> Link: 
> https://lore.kernel.org/all/b0b1863f-40f4-d78e-7bb7-dc4312449d9e@sealevel.com/

Should be a single line.

> 

No blank lines in the tag block.

...

> +	generic_rs485_config(port, termios, rs485);

> +	if (rs485->flags & SER_RS485_ENABLED) {

What I meant is to have

	if (!)rs485->flags & SER_RS485_ENABLED))
		return 0;

here, which allows you to reduce indentation level in the below block.

> +		/* Set EFR[4]=1 to enable enhanced feature registers */
> +		writeb(readb(p + UART_XR_EFR) | UART_EFR_ECB, p + UART_XR_EFR);
> +
> +		/* Set MCR to use DTR as Auto-RS485 Enable signal */
> +		writeb(UART_MCR_OUT1, p + UART_MCR);
> +
> +		/* Store original LCR and set LCR[7]=1 to enable access to DLD register */
> +		old_lcr = readb(p + UART_LCR);
> +		writeb(old_lcr | UART_LCR_DLAB, p + UART_LCR);
> +
> +		/* Set DLD[7]=1 for inverted RS485 Enable logic */
> +		writeb(readb(p + UART_EXAR_DLD) | UART_EXAR_DLD_485_POLARITY, p + UART_EXAR_DLD);
> +
> +		writeb(old_lcr, p + UART_LCR);
> +    }
> +
> +	return 0;

...

> +static int pci_sealevel_setup(struct exar8250 *priv, struct pci_dev *pcidev,
> +		   struct uart_8250_port *port, int idx)
> +{
> +	int ret = pci_xr17v35x_setup(priv, pcidev, port, idx);

> +	port->port.rs485_config = sealevel_rs485_config;

This is incorrect in a way that we do not assign return values in case it is
an error path. This will be prone to mistakes on the caller side.

	int ret;

	ret = ...
	if (ret)
		return ret;

	...

	return 0;

> +	return ret;
> +}

...

> +static const struct exar8250_board pbn_sealevel_16 = {
> +	.num_ports	= 16,

> +    .setup		= pci_sealevel_setup,

Here is the indentation issue. Use leading TABs.

> +	.exit		= pci_xr17v35x_exit,
> +};

...

> +#define SEALEVEL_DEVICE(devid, bd) {			\
> +	PCI_DEVICE_SUB(					\
> +		PCI_VENDOR_ID_EXAR,			\
> +		PCI_DEVICE_ID_EXAR_##devid,		\
> +		PCI_VENDOR_ID_SEALEVEL,			\

> +		PCI_ANY_ID), 0, 0,	\

Seems trailing \ is indented wrongly, missing TAB?

> +		(kernel_ulong_t)&bd			\
> +	}

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2023-09-06 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 16:06 [PATCH V4 2/2] serial: exar: Add RS-485 support for Sealevel XR17V35X based cards Matthew Howell
2023-09-06 10:06 ` Ilpo Järvinen
2023-09-06 13:31   ` Matthew Howell
2023-09-06 14:01     ` Ilpo Järvinen
2023-09-06 13:44 ` Andy Shevchenko [this message]
2023-09-06 15:05   ` Matthew Howell
2023-09-06 15:13     ` Andy Shevchenko
2023-09-11 13:22       ` Matthew Howell
2023-09-11 13:37         ` Andy Shevchenko

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=ZPiCPJYfiR9ZfVJC@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=darren.beeson@sealevel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=james.olson@sealevel.com \
    --cc=jeff.baldwin@sealevel.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=matthew.howell@sealevel.com \
    --cc=ryan.wenglarz@sealevel.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