From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <linux-omap@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <kishon@ti.com>,
<vigneshr@ti.com>
Subject: Re: [PATCH v2 net-next] net: ethernet: ti: davinci_mdio: Add workaround for errata i2329
Date: Tue, 16 Aug 2022 09:56:17 +0530 [thread overview]
Message-ID: <43c7ea8b-f0ca-7f06-02b7-acf677a6f21d@ti.com> (raw)
In-Reply-To: <YvZ3uc0xi18C1g5t@lunn.ch>
On 12/08/22 9:24 pm, Andrew Lunn wrote:
>> sh_eth is not configured for autosuspend and uses only pm_runtime_put().
>
> I don't know the runtime power management code very well. We should
> probably ask somebody how does. However:
>
> https://elixir.bootlin.com/linux/latest/source/drivers/base/power/runtime.c#L168
>
> This suggests it should be safe to perform an auto suspend on a device
> which is not configured for auto suspend. To me, it looks like is
> should directly suspend.
I checked the pm_runtime_put() and pm_runtime_put_autosuspend() and I
have quite a few unanswered questions. I do not have much knowledge
about the runtime PM, so I'm not confident about adding the runtime PM
mdiobb_read/mdiobb_write variants in the mdio bitbang core. I would
rather take a safe approach for now and stick with the implementation
submitted in this v2 patch.
Thanks for your feedback on this submission so far. I will fix the two
other comments and send out a v3 patch.
--
Regards,
Ravi
next prev parent reply other threads:[~2022-08-16 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 11:13 Ravi Gunasekaran
2022-08-11 0:30 ` Andrew Lunn
2022-08-11 7:00 ` Ravi Gunasekaran
2022-08-11 12:57 ` Andrew Lunn
2022-08-12 4:36 ` Ravi Gunasekaran
2022-08-12 15:54 ` Andrew Lunn
2022-08-16 4:26 ` Ravi Gunasekaran [this message]
2022-08-13 0:57 ` kernel test robot
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=43c7ea8b-f0ca-7f06-02b7-acf677a6f21d@ti.com \
--to=r-gunasekaran@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®