From: Claudiu Beznea <Claudiu.Beznea@microchip.com>
To: Harini Katakam <harinik@xilinx.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <michals@xilinx.com>,
<appanad@xilinx.com>
Subject: Re: [RFC PATCH 4/5] net: macb: Add support for suspend/resume with full power down
Date: Thu, 3 May 2018 15:23:06 +0300 [thread overview]
Message-ID: <585eabe8-aae4-cfd3-01aa-bad17197a28d@microchip.com> (raw)
In-Reply-To: <CAFcVECK3UO+tckXnTKvLpWe3+RiZ7fyDmS+3JjgOdeQTRwy_FQ@mail.gmail.com>
On 03.05.2018 14:20, Harini Katakam wrote:
> Hi Claudiu,
>
> On Thu, May 3, 2018 at 3:39 PM, Claudiu Beznea
> <Claudiu.Beznea@microchip.com> wrote:
>>
>>
>> On 22.03.2018 15:51, harinikatakamlinux@gmail.com wrote:
>>> From: Harini Katakam <harinik@xilinx.com>
>>>
>>> When macb device is suspended and system is powered down, the clocks
>>> are removed and hence macb should be closed gracefully and restored
>>> upon resume.
>>
>> Is this a power saving mode which shut down the core?
>
> The Ethernet IP is suspended and a majority of the SoC is shut down, yes.
>
> <snip>
>>> + netif_device_detach(netdev);
>>> + } else {
>>> + netif_device_detach(netdev);
>>> + for (q = 0, queue = bp->queues; q < bp->num_queues; ++q, ++queue)
>>> + napi_disable(&queue->napi);
>>> + phy_stop(netdev->phydev);
>>> + phy_suspend(netdev->phydev);
>>> + spin_lock_irqsave(&bp->lock, flags);
>>> + macb_reset_hw(bp);
>>> + spin_unlock_irqrestore(&bp->lock, flags);
>>
>> Wouldn't be simple to just call macb_close() here?
>
> <snip>
>>
>> Wouln't be simpler to call macb_open() here?
>
> No, I think that would be excessive for suspend. This does just
> enough to put the IP into suspend and cut off clocks.
> For ex., the RX and TX buffers are not freed and allocated again
> in this cycle, just the buffer descriptors.
>
For me looks simpler to just call macb_close()/macb_open() in suspend/resume
hooks. Maybe this doesn't fit to your needs... But most of the code you
added in suspend/resume hooks is already present in macb_open()/macb_close(),
except the TX/RX buffers alloc/free.
SAMA5D2 also uses this IP. SAMA5d2 has a power saving mode where core power is cut
off (including this IP). We are using macb_open()/macb_close() + restoring all
few other registers after this (by calling macb_set_rx_mode() and a variant of
macb_set_features() and few other registers). This is not yet mainlined. I was
intending to send soon a version.
Thank you,
Claudiu
> Regards,
> Harini
>
next prev parent reply other threads:[~2018-05-03 12:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 13:51 [RFC PATCH 0/5] Macb power management support for ZynqMP harinikatakamlinux
2018-03-22 13:51 ` [RFC PATCH 1/5] net: macb: Check MDIO state before read/write and use timeouts harinikatakamlinux
2018-03-22 14:47 ` Andrew Lunn
2018-05-03 10:08 ` Claudiu Beznea
2018-05-03 10:58 ` Harini Katakam
2018-03-22 13:51 ` [RFC PATCH 2/5] net: macb: Support clock management for tsu_clk harinikatakamlinux
2018-03-22 13:51 ` [RFC PATCH 3/5] net: macb: Add pm runtime support harinikatakamlinux
2018-05-03 10:09 ` Claudiu Beznea
2018-05-03 11:13 ` Harini Katakam
2018-05-03 12:59 ` Claudiu Beznea
2018-03-22 13:51 ` [RFC PATCH 4/5] net: macb: Add support for suspend/resume with full power down harinikatakamlinux
2018-05-03 10:09 ` Claudiu Beznea
2018-05-03 11:20 ` Harini Katakam
2018-05-03 12:23 ` Claudiu Beznea [this message]
2018-03-22 13:51 ` [RFC PATCH 5/5] net: macb: Add WOL support with ARP harinikatakamlinux
2018-05-04 12:17 ` Claudiu Beznea
2018-05-10 10:37 ` Harini Katakam
2018-05-15 8:39 ` 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=585eabe8-aae4-cfd3-01aa-bad17197a28d@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=appanad@xilinx.com \
--cc=davem@davemloft.net \
--cc=harinik@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.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).