[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MN2PR18MB2528091339990B1E74C21134D3DD0@MN2PR18MB2528.namprd18.prod.outlook.com>
Date: Mon, 29 Jul 2019 07:16:17 +0000
From: Sudarsana Reddy Kalluru <skalluru@...vell.com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Michal Kalderon <mkalderon@...vell.com>,
Ariel Elior <aelior@...vell.com>
Subject: RE: [PATCH net-next v3 0/2] qed*: Support for NVM config attributes.
> -----Original Message-----
> From: David Miller <davem@...emloft.net>
> Sent: Sunday, July 28, 2019 7:43 AM
> To: Sudarsana Reddy Kalluru <skalluru@...vell.com>
> Cc: netdev@...r.kernel.org; Michal Kalderon <mkalderon@...vell.com>;
> Ariel Elior <aelior@...vell.com>
> Subject: Re: [PATCH net-next v3 0/2] qed*: Support for NVM config
> attributes.
>
> From: Sudarsana Reddy Kalluru <skalluru@...vell.com>
> Date: Sat, 27 Jul 2019 18:55:47 -0700
>
> > The patch series adds support for managing the NVM config attributes.
> > Patch (1) adds functionality to update config attributes via MFW.
> > Patch (2) adds driver interface for updating the config attributes.
> >
> > Changes from previous versions:
> > -------------------------------
> > v3: Removed unused variable.
> > v2: Removed unused API.
> >
> > Please consider applying this series to "net-next".
>
> I don't see where an existing ethtool method hooks into and calls this new
> NVM code.
Dave,
The new API/functionality is invoked as part of ethtool flash (ethtool -f) implementation.
Example code path:
ethtool_ops-->flash_device--> qede_flash_device() --> qed_nvm_flash() --> qed_nvm_flash_cfg_write() --> qed_mcp_nvm_set_cfg()
Thanks,
Sudarsana
Powered by blists - more mailing lists