mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Werner <andre.werner@systec-electronic.com>
To: Maarten Brock <Maarten.Brock@sttls.nl>
Cc: Andre Werner <andre.werner@systec-electronic.com>,
	 "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	 "jirislaby@kernel.org" <jirislaby@kernel.org>,
	 "hvilleneuve@dimonoff.com" <hvilleneuve@dimonoff.com>,
	 "andy@kernel.org" <andy@kernel.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	 "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	 "lech.perczak@camlingroup.com" <lech.perczak@camlingroup.com>
Subject: Re: [External Email] RE: [PATCH v2] serial: sc16is7xx: Extend IRQ check for negative values
Date: Sat, 18 Jan 2025 18:20:16 +0100 (CET)	[thread overview]
Message-ID: <23799bf9-c61b-f528-e0e5-03a96d232ecc@systec-electronic.com> (raw)
In-Reply-To: <AS8PR05MB9810FA4CE091AD28EEE9B73683E52@AS8PR05MB9810.eurprd05.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

Dear Maarten,

> > -----Original Message-----
> > Fix the IRQ check to treat the negative values as No IRQ.
>
> It seems to me that this is a real fix and needs a Fixes tag.
> See below.
>
> > Signed-off-by: Andre Werner <andre.werner@systec-electronic.com>
> > ---
> > diff --git a/drivers/tty/serial/sc16is7xx.c b/drivers/tty/serial/sc16is7xx.c
> > index 7b51cdc274fd..560f45ed19ae 100644
> > --- a/drivers/tty/serial/sc16is7xx.c
> > +++ b/drivers/tty/serial/sc16is7xx.c
> > @@ -1561,7 +1561,7 @@ int sc16is7xx_probe(struct device *dev, const struct
> > sc16is7xx_devtype *devtype,
> >  	/* Always ask for fixed clock rate from a property. */
> >  	device_property_read_u32(dev, "clock-frequency", &uartclk);
> >
> > -	s->polling = !!irq;
> > +	s->polling = (irq <= 0);
>
> When irq>=0 these two lines above have a different outcome!
> irq==0   =>   !!irq==false   <=>   (irq<=0)==true
> irq==1   =>   !!irq==true   <=>   (irq<=0)==false

Thanks for the advice. I have not seen this all the time I looked at the
code. I accidentally forget to delete the second '!' as I did with the code
tested at the embedded device. Thanks for the advice.

Should I need to submit this patch again with a Fixup prefix or what needs
to be done?

>
> >  	if (s->polling)
> >  		dev_dbg(dev,
> >  			"No interrupt pin definition, falling back to polling mode\n");
>
> Kind regards,
> Maarten
>

Regards,
André

  reply	other threads:[~2025-01-18 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 17:18 Andre Werner
2025-01-18  7:34 ` Greg KH
2025-01-18  8:41   ` Jiri Slaby
2025-01-18 19:28   ` [External Email] " Andre Werner
2025-01-19  6:48     ` Greg KH
2025-01-18 12:14 ` Maarten Brock
2025-01-18 17:20   ` Andre Werner [this message]
2025-01-19  8:00     ` [External Email] " Jiri Slaby

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=23799bf9-c61b-f528-e0e5-03a96d232ecc@systec-electronic.com \
    --to=andre.werner@systec-electronic.com \
    --cc=Maarten.Brock@sttls.nl \
    --cc=andy@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jirislaby@kernel.org \
    --cc=lech.perczak@camlingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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®