From: Yixun Lan <dlan@gentoo.org>
To: Alex Elder <elder@riscstar.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Thomas Gleixner <tglx@linutronix.de>,
Inochi Amaoto <inochiama@gmail.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 1/2] irqdomain: support three-cell scheme interrupts
Date: Thu, 27 Feb 2025 20:41:55 +0000 [thread overview]
Message-ID: <20250227204155-GYA51171@gentoo> (raw)
In-Reply-To: <8fce8a9c-7946-4e3c-bbf3-25f8b4f4466f@riscstar.com>
On 10:12 Thu 27 Feb , Alex Elder wrote:
> On 2/27/25 5:24 AM, Yixun Lan wrote:
> > The is a prerequisite patch to support parsing three-cell
> > interrupts which encoded as <instance hwirq irqflag>,
> > the translate function will always retrieve irq number and
> > flag from last two cells.
> >
> > Signed-off-by: Yixun Lan <dlan@gentoo.org>
> > ---
> > kernel/irq/irqdomain.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> > index ec6d8e72d980f604ded2bfa2143420e0e0095920..cb874ab5e54a4763d601122becd63b6d759e55d2 100644
> > --- a/kernel/irq/irqdomain.c
> > +++ b/kernel/irq/irqdomain.c
> > @@ -1208,10 +1208,17 @@ int irq_domain_translate_twocell(struct irq_domain *d,
> > unsigned long *out_hwirq,
> > unsigned int *out_type)
> > {
>
> This function is meant for "twocell". There is also another function
> irq_domain_translate_onecell(). Why don't you just create
> irq_domain_translate_threecell" instead?
>
good question!
it's too many changes for adding "threecell" which I thought not worth
the effort, or maybe we can rename the function to *twothreecell()?
I'm not sure which way to go is the best, ideas from maintainer are
welcome
>
> > + u32 irq, type;
> > +
> > if (WARN_ON(fwspec->param_count < 2))
> > return -EINVAL;
> > - *out_hwirq = fwspec->param[0];
> > - *out_type = fwspec->param[1] & IRQ_TYPE_SENSE_MASK;
> > +
> > + irq = fwspec->param_count - 2;
> > + type = fwspec->param_count - 1;
no matter two or three cell, it's always parse the last two cells,
virtually they are same syntax, which can reuse the *_translate_twocell()
function perfectly..
> > +
> > + *out_hwirq = fwspec->param[irq];
> > + *out_type = fwspec->param[type] & IRQ_TYPE_SENSE_MASK;
> > +
> > return 0;
> > }
> > EXPORT_SYMBOL_GPL(irq_domain_translate_twocell);
> >
>
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@gentoo.org>
To: Alex Elder <elder@riscstar.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Thomas Gleixner <tglx@linutronix.de>,
Inochi Amaoto <inochiama@gmail.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 1/2] irqdomain: support three-cell scheme interrupts
Date: Thu, 27 Feb 2025 20:41:55 +0000 [thread overview]
Message-ID: <20250227204155-GYA51171@gentoo> (raw)
In-Reply-To: <8fce8a9c-7946-4e3c-bbf3-25f8b4f4466f@riscstar.com>
On 10:12 Thu 27 Feb , Alex Elder wrote:
> On 2/27/25 5:24 AM, Yixun Lan wrote:
> > The is a prerequisite patch to support parsing three-cell
> > interrupts which encoded as <instance hwirq irqflag>,
> > the translate function will always retrieve irq number and
> > flag from last two cells.
> >
> > Signed-off-by: Yixun Lan <dlan@gentoo.org>
> > ---
> > kernel/irq/irqdomain.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> > index ec6d8e72d980f604ded2bfa2143420e0e0095920..cb874ab5e54a4763d601122becd63b6d759e55d2 100644
> > --- a/kernel/irq/irqdomain.c
> > +++ b/kernel/irq/irqdomain.c
> > @@ -1208,10 +1208,17 @@ int irq_domain_translate_twocell(struct irq_domain *d,
> > unsigned long *out_hwirq,
> > unsigned int *out_type)
> > {
>
> This function is meant for "twocell". There is also another function
> irq_domain_translate_onecell(). Why don't you just create
> irq_domain_translate_threecell" instead?
>
good question!
it's too many changes for adding "threecell" which I thought not worth
the effort, or maybe we can rename the function to *twothreecell()?
I'm not sure which way to go is the best, ideas from maintainer are
welcome
>
> > + u32 irq, type;
> > +
> > if (WARN_ON(fwspec->param_count < 2))
> > return -EINVAL;
> > - *out_hwirq = fwspec->param[0];
> > - *out_type = fwspec->param[1] & IRQ_TYPE_SENSE_MASK;
> > +
> > + irq = fwspec->param_count - 2;
> > + type = fwspec->param_count - 1;
no matter two or three cell, it's always parse the last two cells,
virtually they are same syntax, which can reuse the *_translate_twocell()
function perfectly..
> > +
> > + *out_hwirq = fwspec->param[irq];
> > + *out_type = fwspec->param[type] & IRQ_TYPE_SENSE_MASK;
> > +
> > return 0;
> > }
> > EXPORT_SYMBOL_GPL(irq_domain_translate_twocell);
> >
>
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-02-27 20:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 11:24 [PATCH 0/2] gpio: irq: support describing three-cell interrupts Yixun Lan
2025-02-27 11:24 ` Yixun Lan
2025-02-27 11:24 ` [PATCH 1/2] irqdomain: support three-cell scheme interrupts Yixun Lan
2025-02-27 11:24 ` Yixun Lan
2025-02-27 16:12 ` Alex Elder
2025-02-27 16:12 ` Alex Elder
2025-02-27 20:41 ` Yixun Lan [this message]
2025-02-27 20:41 ` Yixun Lan
2025-02-28 8:44 ` Linus Walleij
2025-02-28 8:44 ` Linus Walleij
2025-02-28 10:52 ` Yixun Lan
2025-02-28 10:52 ` Yixun Lan
2025-02-28 13:44 ` Thomas Gleixner
2025-02-28 13:44 ` Thomas Gleixner
2025-02-27 11:25 ` [PATCH 2/2] gpiolib: support parsing gpio three-cell interrupts scheme Yixun Lan
2025-02-27 11:25 ` Yixun Lan
2025-02-28 9:11 ` Linus Walleij
2025-02-28 9:11 ` Linus Walleij
2025-02-28 10:10 ` Yixun Lan
2025-02-28 10:10 ` Yixun Lan
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=20250227204155-GYA51171@gentoo \
--to=dlan@gentoo.org \
--cc=brgl@bgdev.pl \
--cc=elder@riscstar.com \
--cc=inochiama@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=spacemit@lists.linux.dev \
--cc=tglx@linutronix.de \
/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.