[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OS3PR01MB65935EC20F350036340F3348BAA09@OS3PR01MB6593.jpnprd01.prod.outlook.com>
Date: Mon, 20 Sep 2021 14:08:37 +0000
From: Min Li <min.li.xe@...esas.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "richardcochran@...il.com" <richardcochran@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"andrew@...n.ch" <andrew@...n.ch>
Subject: RE: [PATCH net v2 2/2] ptp: idt82p33: implement double dco time
correction
> > On Fri, Jun 25, 2021 at 02:24:24PM +0000, Min Li wrote:
> > > How would you suggest to implement the change that make the new
> driver behavior optional?
> > I would say, module parameter or debugfs knob.
>
> Aright, in which case devlink or debugfs, please.
>
> > > What's the point of this? Just rename the file in the filesystem.
> >
> > We use this parameter to specify firmware so that module can be
> > autoloaded /etc/modprobe.d/modname.conf
>
> Sorry, I don't understand. The firmware is in /lib/firmware.
> Previously you used a card coded name (whatever FW_FILENAME is,
> "idt82p33xxx.bin"?). This patch adds the ability to change the firmware file
> name by a module param.
>
> Now let me repeat the question - what's the point of user changing the
> requested firmware name if they can simply rename the file?
We have different firmware named after different 1588 profiles. If we rename firmware, it would make
every profile look same and confusing. On the other hand, with this module parameter, we can have phc
module auto start with correct firmware.
Thanks
Min
Powered by blists - more mailing lists