From: <Claudiu.Beznea@microchip.com>
To: <andrew@lunn.ch>
Cc: <harinik@xilinx.com>, <harini.katakam@xilinx.com>,
<Nicolas.Ferre@microchip.com>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<michal.simek@xilinx.com>, <shubhrajyoti.datta@xilinx.com>,
<sai.pavan.boddu@xilinx.com>
Subject: Re: [PATCH v2 1/4] net: macb: Check MDIO state before read/write and use timeouts
Date: Thu, 29 Nov 2018 10:21:56 +0000 [thread overview]
Message-ID: <21fb7dab-04a3-d144-4a05-1f5146787f03@microchip.com> (raw)
In-Reply-To: <20181128003500.GD26096@lunn.ch>
On 28.11.2018 02:35, Andrew Lunn wrote:
>> Then, do you think it would be better to have a new API part of struct
>> mii_bus that drivers should register so that, the mii core to check if the
>> bus is idle before lunching a new request?
>
> I'm not sure that actually brings anything useful. The core does not
> benefit from it, and it does not make the driver simpler.
Ok, thank you for your input.
Claudiu Beznea
>
> Andrew
>
>
next prev parent reply other threads:[~2018-11-29 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 7:07 [PATCH v2 0/4] Macb power management support for ZynqMP Harini Katakam
2018-11-26 7:07 ` [PATCH v2 1/4] net: macb: Check MDIO state before read/write and use timeouts Harini Katakam
2018-11-26 14:39 ` Andrew Lunn
2018-11-27 5:38 ` Harini Katakam
2018-11-26 14:46 ` Claudiu.Beznea
2018-11-26 14:52 ` Andrew Lunn
2018-11-27 5:36 ` Harini Katakam
2018-11-27 10:25 ` Claudiu.Beznea
2018-11-27 10:49 ` Harini Katakam
2018-11-28 0:35 ` Andrew Lunn
2018-11-29 10:21 ` Claudiu.Beznea [this message]
2018-11-26 7:07 ` [PATCH v2 2/4] net: macb: Support clock management for tsu_clk Harini Katakam
2018-11-26 7:07 ` [PATCH v2 3/4] net: macb: Add pm runtime support Harini Katakam
2018-11-26 14:47 ` Andrew Lunn
2018-11-26 14:47 ` Claudiu.Beznea
2018-11-26 7:07 ` [PATCH v2 4/4] net: macb: Add support for suspend/resume with full power down Harini Katakam
2018-11-26 14:46 ` Claudiu.Beznea
2018-11-27 6:25 ` Harini Katakam
2018-11-27 10:31 ` Claudiu.Beznea
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=21fb7dab-04a3-d144-4a05-1f5146787f03@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=harini.katakam@xilinx.com \
--cc=harinik@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=sai.pavan.boddu@xilinx.com \
--cc=shubhrajyoti.datta@xilinx.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).