From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Tony Lindgren <tony@atomide.com>, Andrew Lunn <andrew@lunn.ch>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org,
Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] net: ethernet: cpsw-phy-sel: prefer phandle for phy sel and update binding
Date: Thu, 9 Aug 2018 17:47:59 -0500 [thread overview]
Message-ID: <3db0048e-21e9-60ea-9e6f-a72bd961f33f@ti.com> (raw)
In-Reply-To: <20180809104653.GV99251@atomide.com>
On 08/09/2018 05:46 AM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [180808 13:52]:
>> * Andrew Lunn <andrew@lunn.ch> [180808 12:02]:
>>>
>>> Do you need to handle EPROBE_DEFER here? The phandle points to a
>>> device which has not yet been loaded? I'm not sure exactly where it
>>> will be returned, maybe it is bus_find_device(), but i expect to see
>>> some handling of it somewhere in this function.
>
> If no device is found the driver just produces a warning currently.
> And in that case cpsw attempts to continue with bootloader settings.
>
> And looking at the caller function cpsw_slave_open() it also just
> produces warnings for phy_connect() too..
>
> I agree that in general this this whole pile of cpsw related drivers sure
> could use some better error handling. Starting with making cpsw_slave_open()
> and cpsw_phy_sel() return errors instead of just ignoring them might be a
> good start.
>
> Grygorii, care to add that note of things to do into your cpsw maintainer
> hat?
Right. EPROBE_DEFER not supported for this module as of now.
>
>> With the proper interconnect hierarchy in the device tree there should be
>> no EPROBE_DEFER happening here as the interconnects are probed in the
>> right order with the always on interrupt with system control module first :)
>>
>> But then again, adding support for EPROBE_DEFER here won't hurt either,
>> will take a look.
>
> I'll just add some notes about that to the patch description considering
> the above.
thanks Tony.
--
regards,
-grygorii
prev parent reply other threads:[~2018-08-09 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 8:03 [PATCH] net: ethernet: cpsw-phy-sel: prefer phandle for phy sel and update binding Tony Lindgren
2018-08-08 11:58 ` Andrew Lunn
2018-08-08 13:48 ` Tony Lindgren
2018-08-09 10:46 ` Tony Lindgren
2018-08-09 22:47 ` Grygorii Strashko [this message]
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=3db0048e-21e9-60ea-9e6f-a72bd961f33f@ti.com \
--to=grygorii.strashko@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).