From: Will Deacon <will.deacon@arm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Rob Herring <robh+dt@kernel.org>,
grant.likely@linaro.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, jroedel@suse.de
Subject: Re: [PATCH 6/6] iommu/arm-smmu: Make use of phandle iterators in device-tree parsing
Date: Tue, 29 Mar 2016 18:22:16 +0100 [thread overview]
Message-ID: <20160329172216.GM6745@arm.com> (raw)
In-Reply-To: <1458669509-7178-7-git-send-email-joro@8bytes.org>
Hi Joerg,
On Tue, Mar 22, 2016 at 06:58:29PM +0100, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> Remove the usage of of_parse_phandle_with_args() and replace
> it by the phandle-iterator implementation so that we can
> parse out all of the potentially present 128 stream-ids.
>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> ---
> drivers/iommu/arm-smmu.c | 28 ++++++++++++++++++++++------
> 1 file changed, 22 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index 59ee4b8..413bd64 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -48,7 +48,7 @@
> #include "io-pgtable.h"
>
> /* Maximum number of stream IDs assigned to a single device */
> -#define MAX_MASTER_STREAMIDS MAX_PHANDLE_ARGS
> +#define MAX_MASTER_STREAMIDS 128
>
> /* Maximum number of context banks per SMMU */
> #define ARM_SMMU_MAX_CBS 128
> @@ -349,6 +349,12 @@ struct arm_smmu_domain {
> struct iommu_domain domain;
> };
>
> +struct arm_smmu_phandle_args {
> + struct device_node *np;
> + int args_count;
> + uint32_t args[MAX_MASTER_STREAMIDS];
> +};
> +
> static struct iommu_ops arm_smmu_ops;
>
> static DEFINE_SPINLOCK(arm_smmu_devices_lock);
> @@ -458,7 +464,7 @@ static int insert_smmu_master(struct arm_smmu_device *smmu,
>
> static int register_smmu_master(struct arm_smmu_device *smmu,
> struct device *dev,
> - struct of_phandle_args *masterspec)
> + struct arm_smmu_phandle_args *masterspec)
> {
> int i;
> struct arm_smmu_master *master;
> @@ -1716,7 +1722,8 @@ static int arm_smmu_device_dt_probe(struct platform_device *pdev)
> struct arm_smmu_device *smmu;
> struct device *dev = &pdev->dev;
> struct rb_node *node;
> - struct of_phandle_args masterspec;
> + struct of_phandle_iterator it;
> + struct arm_smmu_phandle_args masterspec;
> int num_irqs, i, err;
>
> smmu = devm_kzalloc(dev, sizeof(*smmu), GFP_KERNEL);
> @@ -1777,9 +1784,14 @@ static int arm_smmu_device_dt_probe(struct platform_device *pdev)
>
> i = 0;
> smmu->masters = RB_ROOT;
> - while (!of_parse_phandle_with_args(dev->of_node, "mmu-masters",
> - "#stream-id-cells", i,
> - &masterspec)) {
> +
> + of_for_each_phandle(&it, err, dev->of_node,
> + "mmu-masters", "#stream-id-cells", 0) {
> + int count = of_phandle_iterator_args(&it, masterspec.args,
> + MAX_MASTER_STREAMIDS);
> + masterspec.np = of_node_get(it.node);
> + masterspec.args_count = count;
> +
> err = register_smmu_master(smmu, dev, &masterspec);
> if (err) {
> dev_err(dev, "failed to add master %s\n",
> @@ -1789,6 +1801,10 @@ static int arm_smmu_device_dt_probe(struct platform_device *pdev)
>
> i++;
> }
> +
> + if (i == 0)
> + goto out_put_masters;
I'm confused by this hunk. If i == 0, then we shouldn't have registered
any masters and therefore out_put_masters won't have anything to do.
In fact, I'm not completely clear on how the of_node refcounting interacts
with your iterators. Does the iterator put the node after you call the
"next" function, or does it increment each thing exactly once?
Will
next prev parent reply other threads:[~2016-03-29 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 17:58 [PATCH 0/6] of: Implement iterator for phandles Joerg Roedel
2016-03-22 17:58 ` [PATCH 1/6] of: Introduce struct of_phandle_iterator Joerg Roedel
2016-03-22 17:58 ` [PATCH 2/6] of: Move phandle walking to of_phandle_iterator_next() Joerg Roedel
2016-03-22 17:58 ` [PATCH 3/6] of: Remove counting special case from __of_parse_phandle_with_args() Joerg Roedel
2016-03-22 17:58 ` [PATCH 4/6] of: Introduce of_for_each_phandle() helper macro Joerg Roedel
2016-03-22 17:58 ` [PATCH 5/6] of: Introduce of_phandle_iterator_args() Joerg Roedel
2016-03-22 17:58 ` [PATCH 6/6] iommu/arm-smmu: Make use of phandle iterators in device-tree parsing Joerg Roedel
2016-03-22 18:38 ` Rob Herring
2016-03-23 11:47 ` [PATCH v2] iommu/arm-smmu: Make use of phandle iterators in device-tree " Joerg Roedel
2016-03-23 15:18 ` kbuild test robot
2016-04-04 14:25 ` Joerg Roedel
2016-03-22 18:53 ` [PATCH 6/6] iommu/arm-smmu: Make use of phandle iterators in " Robin Murphy
2016-03-23 11:51 ` Joerg Roedel
2016-03-29 17:20 ` Will Deacon
2016-03-29 17:22 ` Will Deacon [this message]
2016-04-04 14:24 ` Joerg Roedel
2016-03-22 18:45 ` [PATCH 0/6] of: Implement iterator for phandles Rob Herring
2016-03-23 11:54 ` Joerg Roedel
2016-03-23 20:37 ` Rob Herring
2016-04-04 15:47 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 15:49 [PATCH 0/6 v2] " Joerg Roedel
2016-04-04 15:49 ` [PATCH 6/6] iommu/arm-smmu: Make use of phandle iterators in device-tree parsing Joerg Roedel
2016-04-14 17:16 ` Will Deacon
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=20160329172216.GM6745@arm.com \
--to=will.deacon@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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