linux-kernel - Re: [PATCH] firmware: arm_scmi: Make scmi core independent of transport type

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, 11 Dec 2019 08:13:40 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Sudeep Holla <sudeep.holla@....com>
Cc:     Cristian Marussi <cristian.marussi@....com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Arnd Bergmann <arnd@...db.de>,
        Jassi Brar <jassisinghbrar@...il.com>,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] firmware: arm_scmi: Make scmi core independent of
 transport type

On 10-12-19, 18:46, Sudeep Holla wrote:
> May be to some/small extent.
> 
> 1. max_rx_timeout_ms is firmware dependent, maximum time it expects to
>    complete a synchronous request or acknowledge async request(worst case value).
> 2. max_msg_size is maximum size of the buffer we need to allocate, mostly
>    based on the specification and we don't have any more that 0x80. But
>    the custom/vendor specific protocols may wary and hence I thought of
>    keeping it configurable for platforms.
> 3. max_msg is the maximum number of messages the transport can support.
>    This is currently based on the mailbox layer. For SMC/HVC we can have
>    upto nr_cpus, something different for spci/optee. We must be able to
>    make it transport independent if required.
> 
>    This is mainly used to pre-allocate number of (tx/rx) buffers.

So we can only move max_msg to mailbox file and read it along with ops, right ?

-- 
viresh