| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <e1cbdfe1-dee6-7452-ad61-62cf74fa24f6@arm.com>
Date: Wed, 18 Oct 2017 15:09:28 +0100
From: Andre Przywara <andre.przywara@....com>
To: Philipp Zabel <p.zabel@...gutronix.de>,
linux-kernel@...r.kernel.org
Cc: Alexandru Gagniuc <alex.g@...ptrum.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>,
Baoyou Xie <baoyou.xie@...aro.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>,
Steffen Trumtrar <s.trumtrar@...gutronix.de>,
Dinh Nguyen <dinguyen@...nel.org>,
Andreas Färber <afaerber@...e.de>,
linux-arm-kernel@...ts.infradead.org, kernel@...gutronix.de
Subject: Re: [PATCH v4 3/5] reset: socfpga: use the reset-simple driver
Hi,
On 18/10/17 14:50, Philipp Zabel wrote:
> On Wed, 2017-10-18 at 14:00 +0100, Andre Przywara wrote:
>> Hi,
>
> Thank you for the review.
>
>> On 17/10/17 14:03, Philipp Zabel wrote:
>>> Add reset line status readback, inverted status support, and socfpga
>>> device tree quirks to the simple reset driver, and use it to replace
>>> the socfpga driver.
>>>
>>> Signed-off-by: Philipp Zabel <p.zabel@...gutronix.de>
>>> ---
>>> Changes since v3:
>>> - Rebased onto reset/next
>>> - Only warn about missing altr,modrst-offset property on socfpga
>>> ---
>>> drivers/reset/Kconfig | 10 +--
>>> drivers/reset/Makefile | 1 -
>>> drivers/reset/reset-simple.c | 51 +++++++++++++-
>>> drivers/reset/reset-simple.h | 4 ++
>>> drivers/reset/reset-socfpga.c | 157 ------------------------------------------
>>> 5 files changed, 56 insertions(+), 167 deletions(-)
>>> delete mode 100644 drivers/reset/reset-socfpga.c
>>>
> [...]
>>> diff --git a/drivers/reset/reset-simple.c b/drivers/reset/reset-simple.c
>>> index a5119457cec61..98ff0f924948e 100644
>>> --- a/drivers/reset/reset-simple.c
>>> +++ b/drivers/reset/reset-simple.c
>>> @@ -68,25 +68,58 @@ static int reset_simple_deassert(struct reset_controller_dev *rcdev,
>>> return reset_simple_update(rcdev, id, false);
>>> }
>>>
>>> +static int reset_simple_status(struct reset_controller_dev *rcdev,
>>> + unsigned long id)
>>> +{
>>> + struct reset_simple_data *data = to_reset_simple_data(rcdev);
>>> + int reg_width = sizeof(u32);
>>> + int bank = id / (reg_width * BITS_PER_BYTE);
>>> + int offset = id % (reg_width * BITS_PER_BYTE);
>>> + u32 reg;
>>> +
>>> + reg = readl(data->membase + (bank * reg_width));
>>> +
>>> + return !(reg & BIT(offset)) ^ !data->status_active_low;
>>> +}
>>> +
>>> const struct reset_control_ops reset_simple_ops = {
>>> .assert = reset_simple_assert,
>>> .deassert = reset_simple_deassert,
>>> + .status = reset_simple_status,
>>> };
>>>
>>> /**
>>> * struct reset_simple_devdata - simple reset controller properties
>>> + * @reg_offset: offset between base address and first reset register.
>>> + * @nr_resets: number of resets. If not set, default to resource size in bits.
>>> * @active_low: if true, bits are cleared to assert the reset. Otherwise, bits
>>> * are set to assert the reset.
>>> + * @status_active_low: if true, bits read back as cleared while the reset is
>>> + * asserted. Otherwise, bits read back as set while the
>>> + * reset is asserted.
>>> */
>>> struct reset_simple_devdata {
>>> + u32 reg_offset;
>>> + u32 nr_resets;
>>> bool active_low;
>>> + bool status_active_low;
>>> +};
>>> +
>>> +#define SOCFPGA_NR_BANKS 8
>>> +
>>> +static const struct reset_simple_devdata reset_simple_socfpga = {
>>> + .reg_offset = 0x10,
>
> Here reset_simple_socfpga.reg_offset is set to the default of 0x10.
Ah, right. Sorry, I missed that.
>
>>> + .nr_resets = SOCFPGA_NR_BANKS * 32,
>>> + .status_active_low = true,
>>> };
>>>
>>> static const struct reset_simple_devdata reset_simple_active_low = {
>>> .active_low = true,
>>> + .status_active_low = true,
>>> };
>>>
>>> static const struct of_device_id reset_simple_dt_ids[] = {
>>> + { .compatible = "altr,rst-mgr", .data = &reset_simple_socfpga },
>>> { .compatible = "allwinner,sun6i-a31-clock-reset",
>>> .data = &reset_simple_active_low },
>>> { /* sentinel */ },
>>> @@ -99,6 +132,7 @@ static int reset_simple_probe(struct platform_device *pdev)
>>> struct reset_simple_data *data;
>>> void __iomem *membase;
>>> struct resource *res;
>>> + u32 reg_offset = 0;
>>>
>>> devdata = of_device_get_match_data(dev);
>>>
>>> @@ -118,8 +152,23 @@ static int reset_simple_probe(struct platform_device *pdev)
>>> data->rcdev.ops = &reset_simple_ops;
>>> data->rcdev.of_node = dev->of_node;
>>>
>>> - if (devdata)
>>> + if (devdata) {
>>> + reg_offset = devdata->reg_offset;
>
> And here reg_offset is set to the default of 0x10 on socfpga.
>
>>> + if (devdata->nr_resets)
>>> + data->rcdev.nr_resets = devdata->nr_resets;
>>> data->active_low = devdata->active_low;
>>> + data->status_active_low = devdata->status_active_low;
>>> + }
>>> +
>>> + if (devdata == &reset_simple_socfpga &&
>>
>> Mmh, this pointer comparison looks a bit dodgy. Isn't
>> of_device_is_compatible() the right solution here?
>
> My thinking was, the of_device_is_compatible is already called inside
> of_device_get_match_data, so why call it again and not reuse the result?
>
>> Also semantically, as the property is tied to a certain compatible
>> string (and not to our data structure)?
>
> I agree with this, though. I'll change this line to say:
>
> + if (of_device_is_compatible(dev->of_node, "altr,rst-mgr") &&
Yes, thank you, that is what I was after.
>
> instead.
>
>>> + of_property_read_u32(dev->of_node, "altr,modrst-offset",
>>> + dev_warn(dev,
>>> + "missing altr,modrst-offset property, assuming 0x%x!\n",
>>> + reg_offset);
>>
>> The existing driver falls back to 0x10 if no explicit property is found.
>> Should we copy this here for compatibility reasons? We could simply use:
>> "reg_offset = 0x10;" before the dev_warn().
Giving the binding documentation a second look, I see that
altr,modrst-offset is a *required* property. So shall we actually use
the opportunity here to stop our too generous behaviour of "you are
missing this required property, but let me fix this up for you anyway
this (one more) time" and revert to a more strict return -ENODEV
instead? Otherwise we just proliferate wrong DTs.
Also this would remove this .reg_offset field from our struct.
Cheers,
Andre.
Powered by blists - more mailing lists