[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF=yD-J+qDcGnVkODTReK64Cr+RTVuT3uT8VfAHs-hm0+4arug@mail.gmail.com>
Date: Wed, 28 Oct 2020 16:37:41 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Alex Elder <elder@...aro.org>
Cc: David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, evgreen@...omium.org,
Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>,
cpratapa@...eaurora.org, bjorn.andersson@...aro.org,
sujitka@...omium.org, Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 net 5/5] net: ipa: avoid going past end of resource
group array
On Wed, Oct 28, 2020 at 3:42 PM Alex Elder <elder@...aro.org> wrote:
>
> The minimum and maximum limits for resources assigned to a given
> resource group are programmed in pairs, with the limits for two
> groups set in a single register.
>
> If the number of supported resource groups is odd, only half of the
> register that defines these limits is valid for the last group; that
> group has no second group in the pair.
>
> Currently we ignore this constraint, and it turns out to be harmless,
> but it is not guaranteed to be. This patch addresses that, and adds
> support for programming the 5th resource group's limits.
>
> Rework how the resource group limit registers are programmed by
> having a single function program all group pairs rather than having
> one function program each pair. Add the programming of the 4-5
> resource group pair limits to this function. If a resource group is
> not supported, pass a null pointer to ipa_resource_config_common()
> for that group and have that function write zeroes in that case.
>
> Fixes: cdf2e9419dd91 ("soc: qcom: ipa: main code")
> Tested-by: Sujit Kautkar <sujitka@...omium.org>
> Signed-off-by: Alex Elder <elder@...aro.org>
Acked-by: Willem de Bruijn <willemb@...gle.com>
Powered by blists - more mailing lists