All of lore.kernel.org
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Marc Zyngier <maz@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Biju Das <biju.das.au@gmail.com>
Subject: RE: [PATCH 2/2] pinctrl: renesas: rzg2l: Enable noise filter for GPIO interrupt input
Date: Wed, 20 Sep 2023 09:20:56 +0000	[thread overview]
Message-ID: <TYCPR01MB59338802F3FA5F4EBE73A2E486F9A@TYCPR01MB5933.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <OS0PR01MB5922F7D95277D08A09A19F0C86FBA@OS0PR01MB5922.jpnprd01.prod.outlook.com>

Hi Geert Uytterhoeven,

> Subject: RE: [PATCH 2/2] pinctrl: renesas: rzg2l: Enable noise filter for
> GPIO interrupt input
> 
> Hi Geert,
> 
> > Subject: Re: [PATCH 2/2] pinctrl: renesas: rzg2l: Enable noise filter
> > for GPIO interrupt input
> >
> > Hi Biju,
> >
> > On Mon, Sep 18, 2023 at 3:18 PM Biju Das <biju.das.jz@bp.renesas.com>
> > wrote:
> > > > Subject: Re: [PATCH 2/2] pinctrl: renesas: rzg2l: Enable noise
> > > > filter for GPIO interrupt input
> > > >
> > > > On Mon, Sep 18, 2023 at 2:34 PM Biju Das
> > > > <biju.das.jz@bp.renesas.com>
> > > > wrote:
> > > > > As per RZ/G2L hardware manual Rev.1.30 section 8.7.3 GPIO
> > > > > Interrupt
> > > > > (TINT) and 41.4.1 Operation for GPIO function, we need to set
> > > > > digital noise filter for GPIO interrupt.
> > > > >
> > > > > This patch enables noise filter for GPIO interrupt in
> > > > > rzg2l_gpio_irq_enable() and disable it in rzg2l_gpio_irq_disable().
> > > > >
> > > > > Fixes: db2e5f21a48e ("pinctrl: renesas: pinctrl-rzg2l: Add IRQ
> > > > > domain to handle GPIO interrupt")
> > > > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > > > Tested-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> > > >
> > > > Thanks for your patch!
> > > >
> > > > > --- a/drivers/pinctrl/renesas/pinctrl-rzg2l.c
> > > > > +++ b/drivers/pinctrl/renesas/pinctrl-rzg2l.c
> > > > > @@ -96,6 +96,7 @@
> > > > >  #define PIN(n)                 (0x0800 + 0x10 + (n))
> > > > >  #define IOLH(n)                        (0x1000 + (n) * 8)
> > > > >  #define IEN(n)                 (0x1800 + (n) * 8)
> > > > > +#define FILONOFF(n)            (0x2080 + (n) * 8)
> > > > >  #define ISEL(n)                        (0x2c80 + (n) * 8)
> > > > >  #define PWPR                   (0x3014)
> > > > >  #define SD_CH(n)               (0x3000 + (n) * 4)
> > > >
> > > > LGTM, but shouldn't you configure the Digital Noise Filter Number
> > > > (FILNUM) and Clock Selection (FILCLKSEL) registers, too?
> > >
> > > Currently it uses reset values.
> > >
> > > 00b: 4-stage filter (41.666 ns x 4 = 166.666 ns) (initial value) for
> > > FILNUM and
> > >
> > > 00b: Not divided (initial value) for FILCLKSEL
> > >
> > > Do you mean we should provide these settings to DT, so that it is
> > > customised based on the PCB design and the environment the board is
> > > used in? I guess this will make it easier for customers to make the
> > > required changes for their application.
> >
> > If the optimal values are board-dependent, you should indeed add a way
> > to configure this from DT.
> 
> Looks like the above values are signal based. I am checking with HW person
> about this. I will confirm once I have update on this.

I rechecked this,

As per section 8.7.3 GPIO Interrupt (TINT), It is not a must. But we should have the flexibility to configure through DT.

 "The noise filter function of GPIO pins assigned to TINT can be enabled by GPIO register setting."

The confusion came because of the section "41.4.1 Operation for GPIO Function"

● Set the FILONOFF register when using GPIO to set a digital noise filter for interrupt input and GPIO input.

So I would like to drop this patch and will send separate patches
for configuring it through DT, if anyone plans to use digital noise
filters.

Cheers,
Biju






  reply	other threads:[~2023-09-20  9:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 12:33 [PATCH 0/2] Fix for GPIO interrupts Biju Das
2023-09-18 12:33 ` [PATCH 1/2] pinctrl: renesas: rzg2l: Make reverse order of enable() for disable() Biju Das
2023-09-18 12:54   ` Geert Uytterhoeven
2023-09-18 12:33 ` [PATCH 2/2] pinctrl: renesas: rzg2l: Enable noise filter for GPIO interrupt input Biju Das
2023-09-18 12:57   ` Geert Uytterhoeven
2023-09-18 13:18     ` Biju Das
2023-09-18 13:25       ` Geert Uytterhoeven
2023-09-18 16:49         ` Biju Das
2023-09-20  9:20           ` Biju Das [this message]
2023-09-20 12:20   ` Linus Walleij
2023-09-20 12:37     ` Biju Das
2023-09-20 13:54       ` Linus Walleij
2023-09-20 14:06         ` Biju Das
2023-09-25 13:19           ` Linus Walleij

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=TYCPR01MB59338802F3FA5F4EBE73A2E486F9A@TYCPR01MB5933.jpnprd01.prod.outlook.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=biju.das.au@gmail.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.