[lkml]   [2020]   [Jul]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH net-next RFC 01/13] devlink: Add reload level option to devlink reload command
On Thu, 30 Jul 2020 15:30:45 +0300 Moshe Shemesh wrote:
> >>> My expectations would be that the driver must perform the lowest
> >>> reset level possible that satisfies the requested functional change.
> >>> IOW driver may do more, in fact it should be acceptable for the
> >>> driver to always for a full HW reset (unless --live or other
> >>> constraint is specified).
> >> OK, but some combinations may still not be valid for specific driver
> >> even if it tries lowest level possible.
> > Can you give an example?
> For example take the combination of fw-live-patch and param-init.
> The fw-live-patch needs no re-initialization, while the param-init
> requires driver re-initialization.
> So the only way to do that is to the one command after the other, not
> really combining.

You need to read my responses more carefully. I don't have
fw-live-patch in my proposal. The operation is fw-activate,
--live is independent and an constraint, not an operation.

 \ /
  Last update: 2020-07-31 01:11    [W:0.064 / U:0.092 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site