linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Dhruva Gole <d-gole@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-gpio@vger.kernel.org, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] pinctrl: single: Add compatible for ti,am625-padconf
Date: Mon, 7 Aug 2023 10:07:24 +0300	[thread overview]
Message-ID: <20230807070724.GN14799@atomide.com> (raw)
In-Reply-To: <20230805171508.schg4xquoa24klk5@october>

* Nishanth Menon <nm@ti.com> [230805 17:15]:
> On 10:25-20230805, Dhruva Gole wrote:
> > From: Tony Lindgren <tony@atomide.com>
> > +static const struct pcs_soc_data pinctrl_single_am625 = {
> > +	.flags = PCS_QUIRK_SHARED_IRQ | PCS_CONTEXT_LOSS_OFF,
> > +	.irq_enable_mask = (1 << 29),   /* WKUP_EN */
> > +	.irq_status_mask = (1 << 30),   /* WKUP_EVT */
> > +};
> > +
> 
> Why cant we set this in the k3-pinctrl.h and set it once?

Good idea to define the bit offsets k3-pinctrl.h instead of magic numbers
here :)

> The event will not be generated until wakeup daisy chain is triggered
> anyways.

Yup, and having that happen is enough to show the wake-up reason with
grep wakeup /proc/interrupts :)

> Have you looked at all the padconf registers across devices to ensure
> the WKUP_EN/EVT bits are present? daisy chain feature is used elsewhere
> as well.

The lack of bits at least earlier just meant that attempting to use a
wake-up interrupt would just never trigger. Worth checking though.
Dhruva, care to check if some padconf register have reserved bits for
29 and 30 that might be set high by default?

Regards,

Tony

  reply	other threads:[~2023-08-07  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  4:55 [PATCH] pinctrl: single: Add compatible for ti,am625-padconf Dhruva Gole
2023-08-05 17:15 ` Nishanth Menon
2023-08-07  7:07   ` Tony Lindgren [this message]
2023-08-07  8:09     ` Dhruva Gole
2023-08-07 10:59       ` Tony Lindgren

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=20230807070724.GN14799@atomide.com \
    --to=tony@atomide.com \
    --cc=d-gole@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=vigneshr@ti.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).