[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e63906cf-9f76-4fed-91b0-1a9168b179bd@linaro.org>
Date: Wed, 6 Dec 2023 12:10:17 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Markus Mayer <mmayer@...adcom.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Rob Herring <robh+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Linux ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
Device Tree Mailing List <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/4] memory: brcmstb_dpfe: support DPFE API v4
On 05/12/2023 19:47, Markus Mayer wrote:
> Add support for version 4 of the DPFE API. This new version is largely
> identical to version 3. The main difference is that all commands now
> take the MHS version number as the first argument. Any other arguments
> have been pushed down by one (i.e. what used to be arg0 in v3 is arg1 in
> v4).
>
> Signed-off-by: Markus Mayer <mmayer@...adcom.com>
> ---
...
> +
> static const char *get_error_text(unsigned int i)
> {
> static const char * const error_text[] = {
> @@ -929,8 +954,12 @@ static const struct of_device_id brcmstb_dpfe_of_match[] = {
> { .compatible = "brcm,dpfe-cpu-v1", .data = &dpfe_api_old_v2 },
> { .compatible = "brcm,dpfe-cpu-v2", .data = &dpfe_api_new_v2 },
> { .compatible = "brcm,dpfe-cpu-v3", .data = &dpfe_api_v3 },
> + { .compatible = "brcm,dpfe-cpu-v4", .data = &dpfe_api_v4 },
>
No, use SoC specific compatible.
Best regards,
Krzysztof
Powered by blists - more mailing lists