[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YjCj07kxGh8n45GE@lunn.ch>
Date: Tue, 15 Mar 2022 15:33:55 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc: Chris Packham <chris.packham@...iedtelesis.co.nz>,
huziji@...vell.com, ulf.hansson@...aro.org, robh+dt@...nel.org,
davem@...emloft.net, kuba@...nel.org, linus.walleij@...aro.org,
catalin.marinas@....com, will@...nel.org,
gregory.clement@...tlin.com, sebastian.hesselbarth@...il.com,
adrian.hunter@...el.com, thomas.petazzoni@...tlin.com,
kostap@...vell.com, robert.marko@...tura.hr,
linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 4/8] pinctrl: mvebu: pinctrl driver for 98DX2530 SoC
> > +static struct platform_driver ac5_pinctrl_driver = {
> > + .driver = {
> > + .name = "ac5-pinctrl",
> > + .of_match_table = of_match_ptr(ac5_pinctrl_of_match),
>
> of_match_ptr() does not look correct for OF-only platform. This should
> complain in W=1 compile tests on !OF config.
The Marvell family of SoC which this embedded SoC borrows HW blocks
from can boot using ACPI. I doubt anybody would boot this particularly
SoC using ACPI, but the drivers Chris copied probably do build !OF for
when ACPI is in us.
Andrew
Powered by blists - more mailing lists