From: jeffy.chen@rock-chips.com (JeffyChen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 01/13] iommu/rockchip: Request irqs in rk_iommu_probe()
Date: Wed, 17 Jan 2018 20:46:08 +0800 [thread overview]
Message-ID: <5A5F4590.1060107@rock-chips.com> (raw)
In-Reply-To: <0b341bbd-6823-a041-9cac-e35bdc9e9bdc@arm.com>
Hi Robin,
On 01/17/2018 08:18 PM, Robin Murphy wrote:
>>
>> @@ -91,7 +92,6 @@ struct rk_iommu {
>> void __iomem **bases;
>> int num_mmu;
>> int *irq;
>
> Nit: irq seems to be redundant now as well.
oops, will fix it.
>
>> - int num_irq;
>> bool reset_disabled;
>> struct iommu_device iommu;
>> struct list_head node; /* entry in rk_iommu_domain.iommus */
>> @@ -830,13 +830,6 @@ static int rk_iommu_attach_device(struct
>> iommu_domain *domain,
>> iommu->domain = domain;
>> - for (i = 0; i < iommu->num_irq; i++) {
>> - ret = devm_request_irq(iommu->dev, iommu->irq[i], rk_iommu_irq,
>> - IRQF_SHARED, dev_name(dev), iommu);
>> - if (ret)
>> - return ret;
>> - }
>> -
>> for (i = 0; i < iommu->num_mmu; i++) {
>> rk_iommu_write(iommu->bases[i], RK_MMU_DTE_ADDR,
>> rk_domain->dt_dma);
>> @@ -885,9 +878,6 @@ static void rk_iommu_detach_device(struct
>> iommu_domain *domain,
>> }
>> rk_iommu_disable_stall(iommu);
>> - for (i = 0; i < iommu->num_irq; i++)
>> - devm_free_irq(iommu->dev, iommu->irq[i], iommu);
>> -
>> iommu->domain = NULL;
>> dev_dbg(dev, "Detached from iommu domain\n");
>> @@ -1138,7 +1128,7 @@ static int rk_iommu_probe(struct platform_device
>> *pdev)
>> struct rk_iommu *iommu;
>> struct resource *res;
>> int num_res = pdev->num_resources;
>> - int err, i;
>> + int err, i, irq, num_irq;
>> iommu = devm_kzalloc(dev, sizeof(*iommu), GFP_KERNEL);
>> if (!iommu)
>> @@ -1165,23 +1155,17 @@ static int rk_iommu_probe(struct
>> platform_device *pdev)
>> if (iommu->num_mmu == 0)
>> return PTR_ERR(iommu->bases[0]);
>> - iommu->num_irq = platform_irq_count(pdev);
>> - if (iommu->num_irq < 0)
>> - return iommu->num_irq;
>> - if (iommu->num_irq == 0)
>> - return -ENXIO;
>> -
>> - iommu->irq = devm_kcalloc(dev, iommu->num_irq, sizeof(*iommu->irq),
>> - GFP_KERNEL);
>> - if (!iommu->irq)
>> - return -ENOMEM;
>> -
>> - for (i = 0; i < iommu->num_irq; i++) {
>> - iommu->irq[i] = platform_get_irq(pdev, i);
>> - if (iommu->irq[i] < 0) {
>> - dev_err(dev, "Failed to get IRQ, %d\n", iommu->irq[i]);
>> + num_irq = of_irq_count(dev->of_node);
>
> To follow up on the other reply, I'm not sure you really need to count
> the IRQs beforehand at all - you're going to be looping through
> platform_get_irq() and handling errors anyway, so you may as well just
> start at 0 and keep going until -ENOENT (or use platform_get_resource()
> to double-check whether an index should be valid, as we do in arm_smmu).
ok, will do that.
>
> Otherwise, it looks like everything that the IRQ handler needs in the
> iommu struct (dev, num_mmu and bases) is already initialised by this
> point, so we should be OK with respect to races.
ok.
>
> Robin.
next prev parent reply other threads:[~2018-01-17 12:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180116132540.18939-1-jeffy.chen@rock-chips.com>
[not found] ` <20180116132540.18939-3-jeffy.chen@rock-chips.com>
2018-01-17 4:23 ` [PATCH v2 02/13] iommu/rockchip: Suppress unbinding Tomasz Figa
2018-01-17 5:32 ` Tomasz Figa
[not found] ` <20180116132540.18939-5-jeffy.chen@rock-chips.com>
2018-01-17 5:22 ` [PATCH v2 04/13] iommu/rockchip: Fix error handling in probe Tomasz Figa
[not found] ` <20180116132540.18939-6-jeffy.chen@rock-chips.com>
2018-01-17 5:26 ` [PATCH v2 05/13] iommu/rockchip: Fix error handling in init Tomasz Figa
[not found] ` <5A5EF7D3.90405@rock-chips.com>
2018-01-17 7:19 ` Tomasz Figa
2018-01-17 12:27 ` Tomasz Figa
2018-01-17 11:36 ` Robin Murphy
[not found] ` <20180116132540.18939-11-jeffy.chen@rock-chips.com>
2018-01-17 5:37 ` [PATCH v2 10/13] iommu/rockchip: Use IOMMU device for dma mapping operations Tomasz Figa
[not found] ` <20180116132540.18939-12-jeffy.chen@rock-chips.com>
2018-01-17 5:44 ` [PATCH v2 11/13] iommu/rockchip: Use OF_IOMMU to attach devices automatically Tomasz Figa
[not found] ` <5A5EF94E.7010806@rock-chips.com>
2018-01-17 7:30 ` Tomasz Figa
2018-01-17 7:47 ` JeffyChen
[not found] ` <20180116132540.18939-13-jeffy.chen@rock-chips.com>
2018-01-17 6:20 ` [PATCH v2 12/13] iommu/rockchip: Add runtime PM support Tomasz Figa
[not found] ` <5A5EFAB2.7040001@rock-chips.com>
2018-01-17 7:38 ` Tomasz Figa
2018-01-17 7:52 ` JeffyChen
2018-01-17 8:48 ` JeffyChen
[not found] ` <20180116132540.18939-2-jeffy.chen@rock-chips.com>
2018-01-17 4:21 ` [PATCH v2 01/13] iommu/rockchip: Request irqs in rk_iommu_probe() Tomasz Figa
[not found] ` <5A5EF672.6040304@rock-chips.com>
2018-01-17 7:16 ` Tomasz Figa
2018-01-17 7:45 ` JeffyChen
2018-01-17 12:18 ` Robin Murphy
2018-01-17 12:46 ` JeffyChen [this message]
[not found] ` <20180116132540.18939-10-jeffy.chen@rock-chips.com>
2018-01-17 12:31 ` [PATCH v2 09/13] iommu/rockchip: Use iommu_group_get_for_dev() for add_device Robin Murphy
2018-01-17 12:47 ` JeffyChen
2018-01-17 12:53 ` JeffyChen
[not found] ` <20180116132540.18939-14-jeffy.chen@rock-chips.com>
2018-01-17 13:00 ` [PATCH v2 13/13] iommu/rockchip: Support sharing IOMMU between masters Robin Murphy
2018-01-17 13:32 ` JeffyChen
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=5A5F4590.1060107@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.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).