linux-kernel - Re: [PATCH v2 0/8] SCMI vendor protocols and modularization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 4 Nov 2020 11:15:37 -0500
From:   Thara Gopinath <thara.gopinath@...aro.org>
To:     Cristian Marussi <cristian.marussi@....com>,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc:     sudeep.holla@....com, lukasz.luba@....com,
        james.quinlan@...adcom.com, Jonathan.Cameron@...wei.com,
        f.fainelli@...il.com, etienne.carriere@...aro.org,
        vincent.guittot@...aro.org, souvik.chakravarty@....com
Subject: Re: [PATCH v2 0/8] SCMI vendor protocols and modularization



On 10/28/20 4:29 PM, Cristian Marussi wrote:
> The current revision of this series still does not address the possibility
> of creating dynamically the SCMI devices: any new protocols must be added
> to the SCMI embedded module device table as of now, while it could be
> desirable to have such devices created dynamically whenever a new protocol
> is added and loaded into the system.

Hi Cristian,

Thanks for v2. I have raised my concerns previously as well on having a 
static table in the main scmi framework for managing the client devices.
This will be a bottleneck not just for vendor protocol addition but also 
to extend the currently supported list of scmi protocols.
I will wait for your v3 (as you mentioned previously) for fixes  around 
this.

-- 
Warm Regards
Thara