From: leizhen <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: "huxinwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org"
<huxinwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
iommu
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Tianhong Ding
<dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2 5/9] iommu/arm-smmu: skip the execution of CMD_PREFETCH_CONFIG
Date: Thu, 9 Jul 2015 09:30:44 +0800 [thread overview]
Message-ID: <559DCEC4.7030104@huawei.com> (raw)
In-Reply-To: <20150708171107.GC6348-5wv7dgnIgG8@public.gmane.org>
On 2015/7/9 1:11, Will Deacon wrote:
> Hi Robin,
>
> FWIW, I already queued this ;)
>
> On Wed, Jul 08, 2015 at 02:03:13PM +0100, Robin Murphy wrote:
>> On 07/07/15 04:30, Zhen Lei wrote:
>>> Hisilicon SMMUv3 devices treat CMD_PREFETCH_CONFIG as a illegal command,
>>> execute it will trigger GERROR interrupt. Although the gerror code manage
>>> to turn the prefetch into a SYNC, and the system can continue to run
>>> normally, but it's ugly to print error information.
>>
>> No mention of the DT binding change, and no corresponding documentation
>> update either.
>
> I've added that.
Thank you very much. You are a real gentleman.
>
>>> Signed-off-by: Zhen Lei <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
>>> ---
>> [...]
>>> +static struct arm_smmu_option_prop arm_smmu_options[] = {
>>> + { ARM_SMMU_OPT_SKIP_PREFETCH, "hisilicon,broken-prefetch-cmd" },
>>> + { 0, NULL},
>>> +};
>> [...]
>>> +static void parse_driver_options(struct arm_smmu_device *smmu)
>>> +{
>>> + int i = 0;
>>> +
>>> + do {
>>> + 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);
>>> +}
>>> +
>>
>> Nitpicking for sure, but I'm still waiting for a good excuse to rewrite
>> this overcomplicated loop logic in the SMMUv2 driver - can't we just
>> treat a static array as a static array and iterate over the thing in the
>> obvious way?
>>
>> for (i = 0; i < ARRAY_SIZE(arm_smmu_options); i++)
>
> I'd rather have consistency with the other driver and I really have no
> personal preference about how we iterate over an array. If you have a
> technical reason to change both the drivers, please send a patch.
>
> Will
>
> .
>
next prev parent reply other threads:[~2015-07-09 1:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 3:30 [PATCH v2 0/9] bugfixs and add support for non-pci devices Zhen Lei
[not found] ` <1436239822-14132-1-git-send-email-thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-07 3:30 ` [PATCH v2 1/9] iommu/arm-smmu: fix the assignment of L1 table log2entries Zhen Lei
2015-07-07 3:30 ` [PATCH v2 2/9] iommu/arm-smmu: fix the index calculation of strtab Zhen Lei
2015-07-07 3:30 ` [PATCH v2 3/9] iommu/arm-smmu: fix the values of ARM64_TCR_IRGN0_SHIFT and ARM64_TCR_ORGN0_SHIFT Zhen Lei
2015-07-07 3:30 ` [PATCH v2 4/9] iommu/arm-smmu: enlarge STRTAB_L1_SZ_SHIFT to support larger sidsize Zhen Lei
2015-07-07 3:30 ` [PATCH v2 5/9] iommu/arm-smmu: skip the execution of CMD_PREFETCH_CONFIG Zhen Lei
[not found] ` <1436239822-14132-6-git-send-email-thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-08 13:03 ` Robin Murphy
2015-07-08 17:11 ` Will Deacon
[not found] ` <20150708171107.GC6348-5wv7dgnIgG8@public.gmane.org>
2015-07-09 1:30 ` leizhen [this message]
2015-07-07 3:30 ` [PATCH v2 6/9] iommu/arm-smmu: to support probe deferral Zhen Lei
[not found] ` <1436239822-14132-7-git-send-email-thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-08 13:13 ` Robin Murphy
[not found] ` <559D21F0.3080202-5wv7dgnIgG8@public.gmane.org>
2015-07-09 11:10 ` leizhen
[not found] ` <559E5693.9060709-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-09 11:27 ` Will Deacon
2015-07-07 3:30 ` [PATCH v2 7/9] iommu/arm-smmu: remove arm_smmu_devices Zhen Lei
[not found] ` <1436239822-14132-8-git-send-email-thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-08 13:13 ` Robin Murphy
[not found] ` <559D2210.50202-5wv7dgnIgG8@public.gmane.org>
2015-07-09 2:43 ` leizhen
2015-07-07 3:30 ` [PATCH v2 8/9] iommu/arm-smmu: rename __arm_smmu_get_pci_sid Zhen Lei
2015-07-07 3:30 ` [PATCH v2 9/9] iommu/arm-smmu: add support for non-pci devices Zhen Lei
[not found] ` <1436239822-14132-10-git-send-email-thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-08 13:22 ` Robin Murphy
2015-07-09 1:56 ` leizhen
[not found] ` <559DD4B6.9000403-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-09 12:01 ` Robin Murphy
[not found] ` <559E6289.6060802-5wv7dgnIgG8@public.gmane.org>
2015-07-10 0:34 ` leizhen
2015-07-07 9:22 ` [PATCH v2 0/9] bugfixs and " 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=559DCEC4.7030104@huawei.com \
--to=thunder.leizhen-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=huxinwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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