From: Robin Murphy <robin.murphy@arm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iommu/arm-smmu-v3: simplify parse_driver_options()
Date: Thu, 9 Jan 2020 13:41:56 +0000 [thread overview]
Message-ID: <1383eeb0-4148-a798-5e24-81ce33013f1d@arm.com> (raw)
In-Reply-To: <20191226095141.30352-2-yamada.masahiro@socionext.com>
On 26/12/2019 9:51 am, Masahiro Yamada wrote:
> Using ARRAY_SIZE() instead of the sentinel is slightly simpler, IMHO.
Given that it's fairly well-decided that we don't want to add any more
of these anyway, I'd be inclined to lose the array/loop machinery
altogether. As it is we'd need a lot more options for it to actually
offer any kind of code size saving.
Robin.
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> drivers/iommu/arm-smmu-v3.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c
> index ed9933960370..b27489b7f9d8 100644
> --- a/drivers/iommu/arm-smmu-v3.c
> +++ b/drivers/iommu/arm-smmu-v3.c
> @@ -676,7 +676,6 @@ struct arm_smmu_option_prop {
> static const struct arm_smmu_option_prop arm_smmu_options[] = {
> { ARM_SMMU_OPT_SKIP_PREFETCH, "hisilicon,broken-prefetch-cmd" },
> { ARM_SMMU_OPT_PAGE0_REGS_ONLY, "cavium,cn9900-broken-page1-regspace"},
> - { 0, NULL},
> };
>
> static inline void __iomem *arm_smmu_page1_fixup(unsigned long offset,
> @@ -696,16 +695,16 @@ static struct arm_smmu_domain *to_smmu_domain(struct iommu_domain *dom)
>
> static void parse_driver_options(struct arm_smmu_device *smmu)
> {
> - int i = 0;
> + int i;
>
> - do {
> + for (i = 0; i < ARRAY_SIZE(arm_smmu_options); i++) {
> if (of_property_read_bool(smmu->dev->of_node,
> arm_smmu_options[i].prop)) {
> smmu->options |= arm_smmu_options[i].opt;
> dev_notice(smmu->dev, "option %s\n",
> arm_smmu_options[i].prop);
> }
> - } while (arm_smmu_options[++i].opt);
> + };
> }
>
> /* Low-level queue manipulation functions */
>
prev parent reply other threads:[~2020-01-09 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 9:51 [PATCH 1/2] iommu/arm-smmu-v3: constify arm_smmu_options[] Masahiro Yamada
2019-12-26 9:51 ` [PATCH 2/2] iommu/arm-smmu-v3: simplify parse_driver_options() Masahiro Yamada
2020-01-09 13:41 ` Robin Murphy [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=1383eeb0-4148-a798-5e24-81ce33013f1d@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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®