From: Dilip Kota <eswara.kota@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>, Lee Jones <lee.jones@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kishon <kishon@ti.com>, DTML <devicetree@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Andriy Shevchenko <andriy.shevchenko@intel.com>,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com, yixin.zhu@intel.com
Subject: Re: [RESEND PATCH v6 1/4] mfd: syscon: Add fwnode_to_regmap
Date: Wed, 29 Apr 2020 13:11:47 +0800 [thread overview]
Message-ID: <a4396fb5-a6e7-8739-560d-9f1242a80773@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a1DP2JNUKP7X=+oPypVZqOHrkByOr3hEXw+3mu2fP49Sw@mail.gmail.com>
On 4/28/2020 6:29 PM, Arnd Bergmann wrote:
> On Tue, Apr 28, 2020 at 12:05 PM Lee Jones <lee.jones@linaro.org> wrote:
>> On Tue, 21 Apr 2020, Dilip Kota wrote:
>>> But, i feel return error for ACPI or oother, looks better because
>>> 'device_node' has fwnode pointer. And provide description
>>> in the header file, mentioning function is success for 'OF' and returns
>>> error for the rest.
>> I don't think this patch adds much to be honest.
>>
>> Better to just do:
>>
>> device_node_get_regmap(to_of_node(fwnode), false);
>>
>> ... from the call site I think.
> Agreed, or just use the of_node pointer consistently in the driver that uses
> it and avoid the use of the fwnode interface entirely when dealing with a
> modern driver that does not need to support board files any more.
>
> Arnd
Ok, I will do it in the driver itself and remove the fwnode_to_regmap()
definition.
Regards,
Dilip
next prev parent reply other threads:[~2020-04-29 5:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 5:04 [PATCH v6 0/4] Add Intel ComboPhy driver Dilip Kota
2020-04-03 5:04 ` [PATCH v6 1/4] mfd: syscon: Add fwnode_to_regmap Dilip Kota
2020-04-06 7:39 ` [RESEND PATCH " Dilip Kota
2020-04-17 9:35 ` Lee Jones
2020-04-21 4:06 ` Dilip Kota
2020-04-28 10:05 ` Lee Jones
2020-04-28 10:29 ` Arnd Bergmann
2020-04-29 5:11 ` Dilip Kota [this message]
2020-04-03 5:04 ` [PATCH v6 2/4] dt-bindings: phy: Add PHY_TYPE_XPCS definition Dilip Kota
2020-04-06 7:39 ` [RESEND PATCH " Dilip Kota
2020-04-03 5:04 ` [PATCH v6 3/4] dt-bindings: phy: Add YAML schemas for Intel ComboPhy Dilip Kota
2020-04-06 7:39 ` [RESEND PATCH " Dilip Kota
2020-04-03 5:04 ` [PATCH v6 4/4] phy: intel: Add driver support for ComboPhy Dilip Kota
2020-04-06 7:39 ` [RESEND PATCH " Dilip Kota
2020-04-06 7:39 ` [RESEND PATCH v6 0/4] Add Intel ComboPhy driver Dilip Kota
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=a4396fb5-a6e7-8739-560d-9f1242a80773@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@arndb.de \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=yixin.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).