From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: <cgel.zte@gmail.com>
Cc: <damien.lemoal@opensource.wdc.com>, <linux-ide@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Minghao Chi <chi.minghao@zte.com.cn>,
"Zeal Robot" <zealci@zte.com.cn>
Subject: Re: [PATCH] ata: Use platform_get_irq() to get the interrupt
Date: Tue, 8 Mar 2022 11:40:35 +0300 [thread overview]
Message-ID: <db22c7c4-8b87-cd6d-469d-2cdd7046a25e@omp.ru> (raw)
In-Reply-To: <20220308025940.2077329-1-chi.minghao@zte.com.cn>
Hello!
Please be more specific in the subject: s/ata:/pata_pxa:/.
On 3/8/22 5:59 AM, cgel.zte@gmail.com wrote:
> From: Minghao Chi (CGEL ZTE) <chi.minghao@zte.com.cn>
>
> platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
> allocation of IRQ resources in DT core code, this causes an issue
> when using hierarchical interrupt domains using "interrupts" property
> in the node as this bypassed the hierarchical setup and messed up the
> irq chaining.
>
> In preparation for removal of static setup of IRQ resource from DT core
> code use platform_get_irq().
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi (CGEL ZTE) <chi.minghao@zte.com.cn>
> ---
> drivers/ata/pata_pxa.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/ata/pata_pxa.c b/drivers/ata/pata_pxa.c
> index 41430f79663c..6394ab4cbc1b 100644
> --- a/drivers/ata/pata_pxa.c
> +++ b/drivers/ata/pata_pxa.c
[...]
> @@ -205,8 +205,8 @@ static int pxa_ata_probe(struct platform_device *pdev)
> /*
> * IRQ pin
> */
> - irq_res = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
> - if (unlikely(irq_res == NULL))
> + irq = platform_get_irq(pdev, 0);
> + if (unlikely(irq < 0))
> return -EINVAL;
Why did you not switch to returning 'irq'? The way it is now, the deferred
probing doesn't work...
[...]
MBR, Sergey
prev parent reply other threads:[~2022-03-08 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 2:59 cgel.zte
2022-03-08 5:49 ` Damien Le Moal
2022-03-08 8:40 ` Sergey Shtylyov [this message]
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=db22c7c4-8b87-cd6d-469d-2cdd7046a25e@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zealci@zte.com.cn \
/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®