linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Villeneuve <hugo@hugovil.com>
To: andy.shevchenko@gmail.com
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	jirislaby@kernel.org, jringle@gridpoint.com,
	tomasz.mon@camlingroup.com, l.perczak@camlintechnologies.com,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	Hugo Villeneuve <hvilleneuve@dimonoff.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v6 5/9] serial: sc16is7xx: fix regression with GPIO configuration
Date: Thu, 1 Jun 2023 20:41:40 -0400	[thread overview]
Message-ID: <20230601204140.3b45c9b97efb36431d058ba7@hugovil.com> (raw)
In-Reply-To: <ZHkN5kEa6yqHdDeL@surfacebook>

On Fri, 2 Jun 2023 00:30:14 +0300
andy.shevchenko@gmail.com wrote:

> Thu, Jun 01, 2023 at 04:18:40PM -0400, Hugo Villeneuve kirjoitti:
> > From: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> > 
> > Commit 679875d1d880 ("sc16is7xx: Separate GPIOs from modem control lines")
> > and commit 21144bab4f11 ("sc16is7xx: Handle modem status lines")
> > changed the function of the GPIOs pins to act as modem control
> > lines without any possibility of selecting GPIO function.
> > 
> > As a consequence, applications that depends on GPIO lines configured
> > by default as GPIO pins no longer work as expected.
> > 
> > Also, the change to select modem control lines function was done only
> > for channel A of dual UART variants (752/762). This was not documented
> > in the log message.
> > 
> > Allow to specify GPIO or modem control line function in the device
> > tree, and for each of the ports (A or B).
> > 
> > Do so by using the new device-tree property named
> > "modem-control-line-ports" (property added in separate patch).
> > 
> > When registering GPIO chip controller, mask-out GPIO pins declared as
> > modem control lines according to this new "modem-control-line-ports"
> > DT property.
> > 
> > Boards that need to have GPIOS configured as modem control lines
> > should add that property to their device tree. Here is a list of
> > boards using the sc16is7xx driver in their device tree and that may
> > need to be modified:
> >     arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts
> >     mips/boot/dts/ingenic/cu1830-neo.dts
> >     mips/boot/dts/ingenic/cu1000-neo.dts
> 
> Almost good, a few remarks and if addressed as suggested,
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> 
> Thank you!
> 
> ...
> 
> > +	if (!s->gpio_valid_mask)
> 
> I would use == 0, but it's up to you. Both will work equally.

Hi,
done.

> > +		return 0;
> 
> ...
> 
> > +static int sc16is7xx_setup_mctrl_ports(struct device *dev)
> 
> Not sure why int if you always return an unsigned value.
> Otherwise return an error code when it's no defined mask
> and check it in the caller.

Changed return type to u8.

 
> > +{
> > +	struct sc16is7xx_port *s = dev_get_drvdata(dev);
> > +	int i;
> > +	int ret;
> > +	int count;
> > +	u32 mctrl_port[2];
> > +	u8 mctrl_mask = 0;
> 
> I would return 0 directly in the first two cases and split an assignment closer
> to the first user.
> 
> > +	count = device_property_count_u32(dev, "nxp,modem-control-line-ports");
> > +	if (count < 0 || count > ARRAY_SIZE(mctrl_port))
> > +		return mctrl_mask;
> 
> 		return 0;

Done.


> > +	ret = device_property_read_u32_array(dev, "nxp,modem-control-line-ports",
> > +					     mctrl_port, count);
> > +	if (ret)
> > +		return mctrl_mask;
> 
> 		return 0;

Done.


> 	mctrl_mask = 0;

Done.

 
> > +	for (i = 0; i < count; i++) {
> > +		/* Use GPIO lines as modem control lines */
> > +		if (mctrl_port[i] == 0)
> > +			mctrl_mask |= SC16IS7XX_IOCONTROL_MODEM_A_BIT;
> > +		else if (mctrl_port[i] == 1)
> > +			mctrl_mask |= SC16IS7XX_IOCONTROL_MODEM_B_BIT;
> > +	}
> 
> > +	if (!mctrl_mask)
> > +		return mctrl_mask;
> 
> Maybe positive one?
> 	if (mctrl_mask)
> 		regmap_update_bits(...);

I used negative to save on indentation, but it also fits by converting it to positive, so done.

 
> > +	regmap_update_bits(s->regmap,
> > +			   SC16IS7XX_IOCONTROL_REG << SC16IS7XX_REG_SHIFT,
> > +			   SC16IS7XX_IOCONTROL_MODEM_A_BIT |
> > +			   SC16IS7XX_IOCONTROL_MODEM_B_BIT, mctrl_mask);
> > +
> > +	return mctrl_mask;
> > +}
> 
> ...
> 
> >  	unsigned long freq = 0, *pfreq = dev_get_platdata(dev);
> >  	unsigned int val;
> > +	u8 mctrl_mask = 0;
> 
> This assignment is redundant, so you simply can define it
> 
> >  	u32 uartclk = 0;
> 
> 	u8 mctrl_mask;

Done.

I will send a V7 soon with your Reviewed-by tag.

Thank you,
Hugo.

 
> >  	int i, ret;
> >  	struct sc16is7xx_port *s;
> 
> -- 
> With Best Regards,
> Andy Shevchenko
 

  reply	other threads:[~2023-06-02  0:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 20:18 [PATCH v6 0/9] serial: sc16is7xx: fix GPIO regression and rs485 improvements Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 1/9] serial: sc16is7xx: fix broken port 0 uart init Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 2/9] serial: sc16is7xx: mark IOCONTROL register as volatile Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 3/9] serial: sc16is7xx: refactor GPIO controller registration Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 4/9] dt-bindings: sc16is7xx: Add property to change GPIO function Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 5/9] serial: sc16is7xx: fix regression with GPIO configuration Hugo Villeneuve
2023-06-01 21:30   ` andy.shevchenko
2023-06-02  0:41     ` Hugo Villeneuve [this message]
2023-06-02  1:25       ` Hugo Villeneuve
2023-06-02 12:58         ` Andy Shevchenko
2023-06-02 13:06           ` Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 6/9] serial: sc16is7xx: fix bug when first setting GPIO direction Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 7/9] serial: sc16is7xx: add call to get rs485 DT flags and properties Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 8/9] serial: sc16is7xx: add post reset delay Hugo Villeneuve
2023-06-01 20:18 ` [PATCH v6 9/9] serial: sc16is7xx: improve comments about variants Hugo Villeneuve

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=20230601204140.3b45c9b97efb36431d058ba7@hugovil.com \
    --to=hugo@hugovil.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jirislaby@kernel.org \
    --cc=jringle@gridpoint.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.perczak@camlintechnologies.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomasz.mon@camlingroup.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).