[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16a4a58c-cae6-4b62-859b-3661c052468a@linaro.org>
Date: Thu, 18 Apr 2024 19:51:22 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Witold Sadowski <wsadowski@...vell.com>, linux-kernel@...r.kernel.org,
linux-spi@...r.kernel.org, devicetree@...r.kernel.org
Cc: broonie@...nel.org, robh@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, pthombar@...ence.com,
Piyush Malgujar <pmalgujar@...vell.com>
Subject: Re: [PATCH v3 4/5] spi: cadence: Allow to read basic xSPI
configuration from ACPI
On 18/04/2024 03:13, Witold Sadowski wrote:
> From: Piyush Malgujar <pmalgujar@...vell.com>
>
> These changes enables to read the configs from ACPI tables as required
> for successful probing in ACPI uefi environment.
> In case of ACPI disabled/dts based environment, it will continue to
> read configs from dts as before
>
..
> }
> @@ -924,6 +989,21 @@ static int cdns_xspi_probe(struct platform_device *pdev)
> return 0;
> }
>
> +#ifdef CONFIG_ACPI
> +static const struct acpi_device_id cdns_xspi_acpi_match[] = {
> + {
> + .id = "cdns,xspi-nor",
> + .driver_data = (kernel_ulong_t) &cdns_driver_data,
> + },
> + {
> + .id = "mrvl,xspi-nor",
> + .driver_data = (kernel_ulong_t) &mrvl_driver_data,
UEFI provides compatibles for ACPI? I think that's first such format in
the kernel.
Best regards,
Krzysztof
Powered by blists - more mailing lists