From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] media: exynos4-is: fimc-is: replace duplicate pmu node with phandle
Date: Tue, 8 Aug 2023 15:31:24 +0200 [thread overview]
Message-ID: <d198429e-d8ca-aeea-e59b-a241dacde658@linaro.org> (raw)
In-Reply-To: <20230808114201.ztr22migzzyfsfwq@intel.intel>
On 08/08/2023 13:42, Andi Shyti wrote:
>>>> +static void __iomem *fimc_is_get_pmu_regs(struct device *dev)
>>>> +{
>>>> + struct device_node *node;
>>>> + void __iomem *regs;
>>>> +
>>>> + node = of_parse_phandle(dev->of_node, "samsung,pmu-syscon", 0);
>>>> + if (!node) {
>>>> + dev_warn(dev, "Finding PMU node via deprecated method, update your DTB\n");
>>>> + node = of_get_child_by_name(dev->of_node, "pmu");
>>>> + if (!node)
>>>> + return IOMEM_ERR_PTR(-ENODEV);
>>>
>>> in my opinion this should be:
>>>
>>> ...
>>> if (!node)
>>> return IOMEM_ERR_PTR(-ENODEV);
>>>
>>> dev_warn(dev, "Finding PMU node via deprecated method, update your DTB\n");
>>>
>>> Because if you don't have both "samsung,pmu-syscon and "pmu" then
>>> the warning should not be printed and you need to return -ENODEV.
>>
>> Why not? Warning is correct - the driver is trying to find, thus
>> continuous tense "Finding", PMU node via old method.
>
> Alright, I'll go along with what you're suggesting, but I have to
> say, I find it misleading.
>
> From what I understand, you're requesting an update to the dtb
> because it's using deprecated methods. However, the reality might
> be that the node is not present in any method at all.
>
> Your statement would be accurate if you failed to find the
> previous method but then did end up finding it.
>
> Relying on the present continuous tense for clarity is a bold
> move, don't you think? :)
I just don't think it matters and is not worth resending.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] media: exynos4-is: fimc-is: replace duplicate pmu node with phandle
Date: Tue, 8 Aug 2023 15:31:24 +0200 [thread overview]
Message-ID: <d198429e-d8ca-aeea-e59b-a241dacde658@linaro.org> (raw)
In-Reply-To: <20230808114201.ztr22migzzyfsfwq@intel.intel>
On 08/08/2023 13:42, Andi Shyti wrote:
>>>> +static void __iomem *fimc_is_get_pmu_regs(struct device *dev)
>>>> +{
>>>> + struct device_node *node;
>>>> + void __iomem *regs;
>>>> +
>>>> + node = of_parse_phandle(dev->of_node, "samsung,pmu-syscon", 0);
>>>> + if (!node) {
>>>> + dev_warn(dev, "Finding PMU node via deprecated method, update your DTB\n");
>>>> + node = of_get_child_by_name(dev->of_node, "pmu");
>>>> + if (!node)
>>>> + return IOMEM_ERR_PTR(-ENODEV);
>>>
>>> in my opinion this should be:
>>>
>>> ...
>>> if (!node)
>>> return IOMEM_ERR_PTR(-ENODEV);
>>>
>>> dev_warn(dev, "Finding PMU node via deprecated method, update your DTB\n");
>>>
>>> Because if you don't have both "samsung,pmu-syscon and "pmu" then
>>> the warning should not be printed and you need to return -ENODEV.
>>
>> Why not? Warning is correct - the driver is trying to find, thus
>> continuous tense "Finding", PMU node via old method.
>
> Alright, I'll go along with what you're suggesting, but I have to
> say, I find it misleading.
>
> From what I understand, you're requesting an update to the dtb
> because it's using deprecated methods. However, the reality might
> be that the node is not present in any method at all.
>
> Your statement would be accurate if you failed to find the
> previous method but then did end up finding it.
>
> Relying on the present continuous tense for clarity is a bold
> move, don't you think? :)
I just don't think it matters and is not worth resending.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-08 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 13:12 [PATCH v2 1/3] media: dt-bindings: samsung,exynos4212-fimc-is: replace duplicate pmu node with phandle Krzysztof Kozlowski
2023-08-07 13:12 ` Krzysztof Kozlowski
2023-08-07 13:12 ` [PATCH v2 2/3] media: dt-bindings: samsung,fimc: correct unit addresses in DTS example Krzysztof Kozlowski
2023-08-07 13:12 ` Krzysztof Kozlowski
2023-08-07 13:12 ` [PATCH v2 3/3] media: exynos4-is: fimc-is: replace duplicate pmu node with phandle Krzysztof Kozlowski
2023-08-07 13:12 ` Krzysztof Kozlowski
2023-08-07 23:13 ` Andi Shyti
2023-08-07 23:13 ` Andi Shyti
2023-08-08 6:22 ` Krzysztof Kozlowski
2023-08-08 6:22 ` Krzysztof Kozlowski
2023-08-08 11:42 ` Andi Shyti
2023-08-08 11:42 ` Andi Shyti
2023-08-08 13:31 ` Krzysztof Kozlowski [this message]
2023-08-08 13:31 ` Krzysztof Kozlowski
2023-08-11 9:49 ` Hans Verkuil
2023-08-11 9:49 ` Hans Verkuil
2023-08-15 6:02 ` Krzysztof Kozlowski
2023-08-15 6:02 ` Krzysztof Kozlowski
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=d198429e-d8ca-aeea-e59b-a241dacde658@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.