From: Andrew Davis <afd@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
<linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: ti: gmii-sel: Allow parent to not be syscon node
Date: Mon, 10 Jul 2023 09:38:11 -0500 [thread overview]
Message-ID: <693d7d42-b062-1e01-b920-e13c2d08ca6f@ti.com> (raw)
In-Reply-To: <5ae4bd37-65ee-d6da-1ab6-c1018d9959ec@ti.com>
On 5/15/23 11:05 PM, Siddharth Vadapalli wrote:
> Andrew,
>
> On 16/05/23 01:29, Andrew Davis wrote:
>> If the parent node is not a syscon type, then fallback and check
>> if we can get a regmap from our own node. This no longer forces
>> us to make the parent of this node a syscon node when that might
>> not be appropriate.
>
> Could you please let me know in which cases it is appropriate versus in which
> cases it isn't?
Use of syscon nodes should be discouraged, in most cases they can and should be
avoided. The only time we would need to have a syscon parent is when the register
space contains multiple sub-devices with bit level interleaving.
Most devices should never need syscon, we overuse syscon due to driver like
this that have no other option than to make the parent device a syscon node.
> Is syscon_node_to_regmap() being retained for backward
> compatibility until the device-tree nodes are cleaned up across all devices?
>
Yes, the old way is left only for backwards compatibility.
>>
>> Signed-off-by: Andrew Davis <afd@ti.com>
>> ---
>> drivers/phy/ti/phy-gmii-sel.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/phy/ti/phy-gmii-sel.c b/drivers/phy/ti/phy-gmii-sel.c
>> index 8c667819c39a..1e67ed9a5cf6 100644
>> --- a/drivers/phy/ti/phy-gmii-sel.c
>> +++ b/drivers/phy/ti/phy-gmii-sel.c
>> @@ -435,9 +435,12 @@ static int phy_gmii_sel_probe(struct platform_device *pdev)
>>
>> priv->regmap = syscon_node_to_regmap(node->parent);
>> if (IS_ERR(priv->regmap)) {
>> - ret = PTR_ERR(priv->regmap);
>> - dev_err(dev, "Failed to get syscon %d\n", ret);
>> - return ret;
>> + priv->regmap = device_node_to_regmap(node);
>
> If device_node_to_regmap() can always be used with the corresponding changes
> made to the device-tree nodes, wouldn't it be better to use it directly instead
> of using it as a fallback? (This is based on the assumption that
> syscon_node_to_regmap() is only being retained until the device-tree nodes are
> cleaned up to work with device_node_to_regmap()).
>
Yes, that could work too. I was trying to make the minimal changes here, but
if we feel it works better we can have the default be to check the self node first.
Andrew
>> + if (IS_ERR(priv->regmap)) {
>> + ret = PTR_ERR(priv->regmap);
>> + dev_err(dev, "Failed to get syscon %d\n", ret);
>> + return ret;
>> + }
>> }
>>
>> ret = phy_gmii_sel_init_ports(priv);
>
next prev parent reply other threads:[~2023-07-10 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 19:59 Andrew Davis
2023-05-16 4:05 ` Siddharth Vadapalli
2023-07-10 14:38 ` Andrew Davis [this message]
2023-05-16 18:33 ` Roger Quadros
2023-07-10 14:45 ` Andrew Davis
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=693d7d42-b062-1e01-b920-e13c2d08ca6f@ti.com \
--to=afd@ti.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®