[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f729ae6-8b20-e77c-18f7-cbe093f8a3b9@starfivetech.com>
Date: Wed, 12 Apr 2023 15:52:41 +0800
From: Changhuang Liang <changhuang.liang@...rfivetech.com>
To: Conor Dooley <conor@...nel.org>
CC: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Emil Renner Berthing <kernel@...il.dk>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Walker Chen <walker.chen@...rfivetech.com>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH v1 5/7] soc: starfive: Use call back to parse device tree
resources
On 2023/4/12 5:06, Conor Dooley wrote:
> On Mon, Apr 10, 2023 at 11:47:41PM -0700, Changhuang Liang wrote:
>> Different compatible parse device tree resources work in different ways.
>
> Right now there is only one compatible, so this commit message needs to
> be expanded on to provide more information on your motivation.
>
OK, will add more commit message.
>> Signed-off-by: Changhuang Liang <changhuang.liang@...rfivetech.com>
>
>> static int jh71xx_pmu_init_domain(struct jh71xx_pmu *pmu, int index)
>> {
[...]
>>
>> match_data = of_device_get_match_data(dev);
>> if (!match_data)
>> return -EINVAL;
>>
>> + if (match_data->pmu_parse_dt) {
>
> How can this be false?
>
> Cheers,
> Conor.
Yes, it will not be false, I will delete this if condition
Powered by blists - more mailing lists