[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZS0vtOwDVwSMErK4@smile.fi.intel.com>
Date: Mon, 16 Oct 2023 15:42:28 +0300
From: Andy Shevchenko <andy@...nel.org>
To: Kartik <kkartik@...dia.com>
Cc: thierry.reding@...il.com, jonathanh@...dia.com,
keescook@...omium.org, akpm@...ux-foundation.org, arnd@...db.de,
ulf.hansson@...aro.org, linus.walleij@...aro.org,
pshete@...dia.com, petlozup@...dia.com, frank.li@...o.com,
robh@...nel.org, stefank@...dia.com, pdeschrijver@...dia.com,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v6 7/8] soc/tegra: fuse: Add ACPI support for Tegra194
and Tegra234
On Mon, Oct 16, 2023 at 03:44:35PM +0530, Kartik wrote:
> Add ACPI support for Tegra194 & Tegra243 SoC's. This requires
> following modifications to the probe when ACPI boot is used:
> - Initialize soc data.
> - Add nvmem lookups.
> - Register soc device.
> - use devm_clk_get_optional() instead of devm_clk_get() to get
> fuse->clk, as fuse clocks are not required when using ACPI boot.
>
> Also, drop '__init' keyword for tegra_soc_device_register() as this is also
> used by tegra_fuse_probe() and use dev_err_probe() wherever applicable.
...
> +static const struct acpi_device_id __maybe_unused tegra_fuse_acpi_match[] = {
Drop __maybe_unused along with ACPI_PTR(), they are more confusing than helpful.
> + { "NVDA200F" },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(acpi, tegra_fuse_acpi_match);
> +
> static struct platform_driver tegra_fuse_driver = {
> .driver = {
> .name = "tegra-fuse",
> .of_match_table = tegra_fuse_match,
> + .acpi_match_table = ACPI_PTR(tegra_fuse_acpi_match),
> .pm = &tegra_fuse_pm,
> .suppress_bind_attrs = true,
> },
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists