[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220701145508.xw3zbhldi7lvcwgd@bogus>
Date: Fri, 1 Jul 2022 15:55:08 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Cristian Marussi <cristian.marussi@....com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
james.quinlan@...adcom.com, Jonathan.Cameron@...wei.com,
f.fainelli@...il.com, etienne.carriere@...aro.org,
vincent.guittot@...aro.org, daniel.lezcano@...aro.org,
tarek.el-sherbiny@....com, adrian.slatineanu@....com,
souvik.chakravarty@....com, wleavitt@...vell.com,
wbartczak@...vell.com
Subject: Re: [PATCH v3 5/9] firmware: arm_scmi: Make use of FastChannels
configurable
On Fri, Jul 01, 2022 at 03:47:20PM +0100, Cristian Marussi wrote:
[...]
> ... regarding why, I am using personally this indeed for testing with or
> without FCs without having to change the installed FW blob, BUT the reason
> for upstreaming such an option is that FC support is indeed optional by the
> spec so I thought it would have been acceptabel that you could want to
> configure a platform NOT to use them even though the FW implementation you
> are using, maybe across multiple platforms, supports it.
Yes it is optional. But we use only if F/W advertises that it is available,
so no harm if it is not implemented right ? I don't believe it will save
space in the way config is used and I don't want to push all the code
under the config too.
--
Regards,
Sudeep
Powered by blists - more mailing lists