From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: cgel.zte@gmail.com, s.shtylyov@omp.ru
Cc: 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 V2] ata: pata_pxa: Use platform_get_irq() to get the interrupt
Date: Wed, 9 Mar 2022 15:24:43 +0900 [thread overview]
Message-ID: <d1dfb244-eda3-b5c6-c6bd-c0294a9a4a94@opensource.wdc.com> (raw)
In-Reply-To: <20220309055038.2081317-1-chi.minghao@zte.com.cn>
On 3/9/22 14:50, cgel.zte@gmail.com wrote:
> From: Minghao Chi <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 bypasses the hierarchical setup and messes up the
> irq chaining.
>
> In preparation for removal of static setup of IRQ resource from DT core
> code use platform_get_irq().
>
> v1->v2:
> - Use more specific in the subject: ata: pata_pxa:
> - Switch to returning 'irq'
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> ---
> drivers/ata/pata_pxa.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/ata/pata_pxa.c b/drivers/ata/pata_pxa.c
> index 41430f79663c..340b274d0cad 100644
> --- a/drivers/ata/pata_pxa.c
> +++ b/drivers/ata/pata_pxa.c
> @@ -164,10 +164,10 @@ static int pxa_ata_probe(struct platform_device *pdev)
> struct resource *cmd_res;
> struct resource *ctl_res;
> struct resource *dma_res;
> - struct resource *irq_res;
> struct pata_pxa_pdata *pdata = dev_get_platdata(&pdev->dev);
> struct dma_slave_config config;
> int ret = 0;
> + int irq;
>
> /*
> * Resource validation, three resources are needed:
> @@ -205,9 +205,9 @@ 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))
> - return -EINVAL;
> + irq = platform_get_irq(pdev, 0);
> + if (unlikely(irq < 0))
Please drop the unlikely() here. Not needed. This is not the hot path.
> + return irq;
>
> /*
> * Allocate the host
> @@ -287,7 +287,7 @@ static int pxa_ata_probe(struct platform_device *pdev)
> /*
> * Activate the ATA host
> */
> - ret = ata_host_activate(host, irq_res->start, ata_sff_interrupt,
> + ret = ata_host_activate(host, irq, ata_sff_interrupt,
> pdata->irq_flags, &pxa_ata_sht);
> if (ret)
> dma_release_channel(data->dma_chan);
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-03-09 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 5:50 cgel.zte
2022-03-09 6:24 ` Damien Le Moal [this message]
2022-03-09 7:28 ` [PATCH V3] " cgel.zte
2022-03-09 7:31 ` Damien Le Moal
2022-03-09 8:55 ` Sergei Shtylyov
2022-03-09 9:00 ` Sergey Shtylyov
2022-03-09 8:51 ` Sergey Shtylyov
2022-03-10 2:21 ` Damien Le Moal
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=d1dfb244-eda3-b5c6-c6bd-c0294a9a4a94@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
--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®