From: Joel Stanley <joel@jms.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/xics: Set the IRQ chip data for the ICS native backend
Date: Mon, 13 Sep 2021 23:21:52 +0000 [thread overview]
Message-ID: <CACPK8Xestw5t3y+gzLviVJ-FbfTM4WCYOyQ1nskvgzZOP0rndA@mail.gmail.com> (raw)
In-Reply-To: <20210913134056.3761960-1-clg@kaod.org>
On Mon, 13 Sept 2021 at 13:48, Cédric Le Goater <clg@kaod.org> wrote:
>
> The ICS native driver relies on the IRQ chip data to find the struct
> 'ics_native' describing the ICS controller but it was removed by commit
> 248af248a8f4 ("powerpc/xics: Rename the map handler in a check handler").
> Revert this change to fix the Microwatt SoC platform.
>
> Fixes: 248af248a8f4 ("powerpc/xics: Rename the map handler in a check handler")
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Joel Stanley <joel@jms.id.au>
Thanks Cédric.
> ---
> arch/powerpc/sysdev/xics/xics-common.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/sysdev/xics/xics-common.c b/arch/powerpc/sysdev/xics/xics-common.c
> index 5c1a157a83b8..244a727c6ba4 100644
> --- a/arch/powerpc/sysdev/xics/xics-common.c
> +++ b/arch/powerpc/sysdev/xics/xics-common.c
> @@ -348,9 +348,9 @@ static int xics_host_map(struct irq_domain *domain, unsigned int virq,
> if (xics_ics->check(xics_ics, hwirq))
> return -EINVAL;
>
> - /* No chip data for the XICS domain */
> + /* Let the ICS be the chip data for the XICS domain. For ICS native */
> irq_domain_set_info(domain, virq, hwirq, xics_ics->chip,
> - NULL, handle_fasteoi_irq, NULL, NULL);
> + xics_ics, handle_fasteoi_irq, NULL, NULL);
>
> return 0;
> }
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-09-13 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 13:40 [PATCH] powerpc/xics: Set the IRQ chip data for the ICS native backend Cédric Le Goater
2021-09-13 17:25 ` Gustavo Romero
2021-09-13 17:54 ` Gustavo Romero
2021-09-13 23:21 ` Joel Stanley [this message]
2021-09-19 12:20 ` Michael Ellerman
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=CACPK8Xestw5t3y+gzLviVJ-FbfTM4WCYOyQ1nskvgzZOP0rndA@mail.gmail.com \
--to=joel@jms.id.au \
--cc=clg@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).