netdev - Re: [EXTERNAL] Re: [EXTERNAL] Re: [EXTERNAL] Re: [PATCH] net: phy: dp83tc811: modify list of interrupts enabled at initialization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <E3DBDC45-111F-4744-82A8-95C7D5CCEBE5@ti.com>
Date:   Fri, 10 Sep 2021 00:41:53 +0000
From:   "Modi, Geet" <geet.modi@...com>
To:     Andrew Lunn <andrew@...n.ch>
CC:     "Nagalla, Hari" <hnagalla@...com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Sharma, Vikram" <vikram.sharma@...com>
Subject: Re: [EXTERNAL] Re: [EXTERNAL] Re: [EXTERNAL] Re: [PATCH] net: phy:
 dp83tc811: modify list of interrupts enabled at initialization

Hi Andrew,

As mentioned we want to do this in phases: 
a) this patch to disable the Overvoltage driver interrupt
b) After carefully considering other interrupts, plan a  follow-on patch to take care of other interrupts.

Patch comment will be inline with your suggestion

"The over voltage interrupt is enabled, but if it ever occurs, there is no code to make use of it. So removing it. It
    can re-enabled when HWMON support is added "

Regarfds,
Geet


On 9/9/21, 1:37 PM, "Andrew Lunn" <andrew@...n.ch> wrote:

    > I am planning to have following commit msg;
    > 
    >  
    > 
    > “This feature is not used by our mainstream customers as they have additional

    As i said, this is not your driver, for you customers. It is the Linux
    kernel driver. Please drop all references to your customers. If you
    need to address anybody, it should be the Linux community as a whole,
    or maybe the users of this driver.

    > mechanism to monitor the supply at System level as accuracy requirements are
    > different for each application.  The device is designed with inbuilt monitor
    > with interrupt disabled by default and let user choose if they want to exercise
    > the monitor. However, the driver had this interrupt enabled, the request here
    > is disable it by default in driver however not change in datasheet.  Let user
    > of the driver review the accuracy offered by monitor and if meets the
    > expectation, they can always enable it.”

    I would much more prefer something like...

    The over voltage interrupt is enabled, but if it every occurs, there is
    no code to make use of it. So remove the pointless enabling of it. It
    can re-enabled when HWMON support is added. For the same reason,
    enabling of the interrupts DP83811_RX_ERR_HF_INT_EN,
    DP83811_MS_TRAINING_INT_EN, DP83811_ESD_EVENT_INT_EN,
    DP83811_ENERGY_DET_INT_EN, DP83811_LINK_QUAL_INT_EN,
    DP83811_JABBER_DET_INT_EN, DP83811_POLARITY_INT_EN,
    DP83811_SLEEP_MODE_INT_EN, DP83811_OVERTEMP_INT_EN,
    DP83811_UNDERVOLTAGE_INT_EN is also removed, since there is no code
    which acts on these interrupts.

    And update the patch to fit.

          Andrew