[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZbtjyOBHzVKXu_4H@nanopsycho>
Date: Thu, 1 Feb 2024 10:26:32 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: "David E. Box" <david.e.box@...ux.intel.com>
Cc: netdev@...r.kernel.org, ilpo.jarvinen@...ux.intel.com,
sathyanarayanan.kuppuswamy@...ux.intel.com,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH 4/8] platform/x86/intel/sdsi: Add netlink SPDM transport
Thu, Feb 01, 2024 at 02:07:43AM CET, david.e.box@...ux.intel.com wrote:
[...]
>+ -
>+ name: spdm-req
>+ type: binary
>+ -
>+ name: spdm-rsp
>+ type: binary
I don't understand the need to use netlink for this. Basically what you
do is you just use it to pass binary blobs to and from FW.
Advantages, like well-defined attributes, notifications etc, for which
it makes sense to use Netlink are not utilized at all.
Also, I don't thing it is good idea to have hw-driver-specific genl
family. I'm not aware of anything like that so far. Leave netlink
for use of generic and abstracted APIs.
Can't you just have a simple misc device for this?
Thanks.
>+ -
>+ name: spdm-rsp-size
>+ type: u32
>+ -
>+ name: spdm-req-size
>+ type: u32
>+ -
[...]
Powered by blists - more mailing lists