Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v2 0/8] SCMI vendor protocols and modularization
To:     Cristian Marussi <cristian.marussi@arm.com>,
        linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc:     sudeep.holla@arm.com, lukasz.luba@arm.com,
        james.quinlan@broadcom.com, Jonathan.Cameron@Huawei.com,
        f.fainelli@gmail.com, etienne.carriere@linaro.org,
        vincent.guittot@linaro.org, souvik.chakravarty@arm.com
References: <20201028202914.43662-1-cristian.marussi@arm.com>
From:   Thara Gopinath <thara.gopinath@linaro.org>
Message-ID: <49662d46-ca4a-4173-1d98-6ce7975afcae@linaro.org>
Date:   Wed, 4 Nov 2020 11:15:37 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20201028202914.43662-1-cristian.marussi@arm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


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