From: "Modi, Geet" <geet.modi@ti.com>
To: Andrew Lunn <andrew@lunn.ch>, "Nagalla, Hari" <hnagalla@ti.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sharma, Vikram" <vikram.sharma@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH] net: phy: dp83tc811: modify list of interrupts enabled at initialization
Date: Mon, 6 Sep 2021 20:51:53 +0000 [thread overview]
Message-ID: <99232B33-1C2F-45AF-A259-0868AC7D3FBC@ti.com> (raw)
In-Reply-To: <YTFc6pyEtlRO/4r/@lunn.ch>
Hi Andrew,
This feature is not used by our mainstream customers as they have additional mechanism to monitor the supply at System level.
Hence want to keep it disable by default.
Regards,
Geet
On 9/2/21, 4:23 PM, "Andrew Lunn" <andrew@lunn.ch> wrote:
On Thu, Sep 02, 2021 at 02:09:44PM -0500, hnagalla@ti.com wrote:
> From: Hari Nagalla <hnagalla@ti.com>
>
> Disable the over voltage interrupt at initialization to meet typical
> application requirement.
Are you saying it is typical to supply too high a voltage?
Andrew
next prev parent reply other threads:[~2021-09-06 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 19:09 [PATCH] net: phy: dp83tc811: modify list of interrupts enabled at initialization hnagalla
2021-09-02 23:23 ` Andrew Lunn
2021-09-06 20:51 ` Modi, Geet [this message]
2021-09-07 14:02 ` [EXTERNAL] " Andrew Lunn
[not found] ` <E61A9519-DBA6-4931-A2A0-78856819C362@ti.com>
2021-09-09 20:37 ` [EXTERNAL] " Andrew Lunn
2021-09-10 0:41 ` [EXTERNAL] " Modi, Geet
2021-09-10 1:30 ` Andrew Lunn
2021-09-10 1:42 ` [EXTERNAL] " Modi, Geet
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=99232B33-1C2F-45AF-A259-0868AC7D3FBC@ti.com \
--to=geet.modi@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hnagalla@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vikram.sharma@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;
as well as URLs for NNTP newsgroup(s).