Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Sudeep Holla <sudeep.holla@arm.com>
To:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        Cristian Marussi <cristian.marussi@arm.com>
Cc:     Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH] firmware: arm_scmi: Fix xfers allocation on RX channel
Date:   Mon, 17 Apr 2023 13:43:51 +0100
Message-Id: <168173500399.1886197.2762979819765120755.b4-ty@arm.com>
In-Reply-To: <20230326203449.3492948-1-cristian.marussi@arm.com>
References: <20230326203449.3492948-1-cristian.marussi@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sun, 26 Mar 2023 21:34:49 +0100, Cristian Marussi wrote:
> Two distinct pools of xfer descriptors are allocated at initialization
> time: one (TX) used to provide xfers to track commands and their replies
> (or delayed replies) and another (RX) to pick xfers from to be used for
> processing notifications.
> 
> Such pools, though, are allocated globally to be used by the whole SCMI
> instance, they are not allocated per-channel and as such the allocation of
> notifications xfers cannot be simply skipped if no RX channel was found for
> the Base protocol common channel, because there could be defined more
> optional per-protocol dedicated channels that instead support RX channels.
> 
> [...]

Applied to sudeep.holla/linux (for-next/scmi/fixes), thanks!

[1/1] firmware: arm_scmi: Fix xfers allocation on RX channel
	https://git.kernel.org/sudeep.holla/c/b2ccba9e8cdc
--
Regards,
Sudeep