[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZQF+PHTYDZRX1gql@nanopsycho>
Date: Wed, 13 Sep 2023 11:17:48 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Jinjian Song <songjinjian@...mail.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, corbet@....net, loic.poulain@...aro.org,
ryazanov.s.a@...il.com, johannes@...solutions.net,
chandrashekar.devegowda@...el.com, linuxwwan@...el.com,
chiranjeevi.rapolu@...ux.intel.com, haijun.liu@...iatek.com,
m.chetan.kumar@...ux.intel.com, ricardo.martinez@...ux.intel.com,
netdev@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, nmarupaka@...gle.com,
vsankar@...ovo.com, danielwinkler@...gle.com
Subject: Re: [net-next v4 0/5] net: wwan: t7xx: fw flashing & coredump support
Tue, Sep 12, 2023 at 11:48:40AM CEST, songjinjian@...mail.com wrote:
>Adds support for t7xx wwan device firmware flashing & coredump collection
>using devlink.
I don't believe that use of devlink is correct here. It seems like a
misfit. IIUC, what you need is to communicate with the modem. Basically
a communication channel to modem. The other wwan drivers implement these
channels in _ctrl.c files, using multiple protocols. Why can't you do
something similar and let devlink out of this please?
Until you put in arguments why you really need devlink and why is it a
good fit, I'm against this. Please don't send any other versions of this
patchset that use devlink.
NACK.
Powered by blists - more mailing lists