Received-SPF: pass (google.com: domain of linux-kernel+bounces-10392-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-1364-ga51d5fd3b7-fm-20231219.001-ga51d5fd3
Precedence: bulk
MIME-Version: 1.0
Message-Id: <04af87cb-1a37-4ce5-8a02-1ae909b0d9eb@app.fastmail.com>
In-Reply-To: <e0be87889c7d2a79e0d559ffcf9b08888f994b08.camel@maquefel.me>
References: <20231212-ep93xx-v6-0-c307b8ac9aa8@maquefel.me>
 <20231212-ep93xx-v6-8-c307b8ac9aa8@maquefel.me>
 <ZXn51mcYslZzQ3y-@smile.fi.intel.com>
 <e0be87889c7d2a79e0d559ffcf9b08888f994b08.camel@maquefel.me>
Date: Sat, 23 Dec 2023 11:32:02 +0000
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nikita Shubin" <nikita.shubin@maquefel.me>,
 "Andy Shevchenko" <andriy.shevchenko@intel.com>
Cc: "Conor.Dooley" <conor.dooley@microchip.com>,
 "Ulf Hansson" <ulf.hansson@linaro.org>, "Joel Stanley" <joel@jms.id.au>,
 "Walker Chen" <walker.chen@starfivetech.com>,
 =?UTF-8?Q?Jonathan_Neusch=C3=A4fer?= <j.neuschaefer@gmx.net>,
 "Huisong Li" <lihuisong@huawei.com>, "Wei Xu" <xuwei5@hisilicon.com>,
 "Emil Renner Berthing" <kernel@esmil.dk>,
 "Linus Walleij" <linus.walleij@linaro.org>,
 "Alexander Sverdlin" <alexander.sverdlin@gmail.com>,
 "Hal Feng" <hal.feng@starfivetech.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 08/40] soc: Add SoC driver for Cirrus ep93xx
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 23, 2023, at 10:06, Nikita Shubin wrote:
> On Wed, 2023-12-13 at 20:37 +0200, Andy Shevchenko wrote:
>> On Tue, Dec 12, 2023 at 11:20:25AM +0300, Nikita Shubin wrote:

>>=20
>> Maybe
>>=20
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0strict device *dev =3D=
 &pdev->dev;
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0enum ep93xx_soc_model=
 model;
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0...
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0model =3D (enum
>> ep93xx_soc_model)(uintptr_t)device_get_match_data(dev);
>>=20
>> ?

You can just skip the second cast:

    model =3D (uintptr_t)device_get_match_data(dev);


or even better, since the only thing you look up by model is the
string put the string directly into the data:

+static const struct of_device_id ep9301_syscon_of_device_ids[] =3D {
+	{ .compatible	=3D "cirrus,ep9301-syscon", .data =3D "pinctrl-ep9301" },
+	{ .compatible	=3D "cirrus,ep9302-syscon", .data =3D "pinctrl-ep9301" },
+	{ .compatible	=3D "cirrus,ep9307-syscon", .data =3D "pinctrl-ep9307" },
+	{ .compatible	=3D "cirrus,ep9312-syscon", .data =3D "pinctrl-ep9312" },
+	{ .compatible	=3D "cirrus,ep9315-syscon", .data =3D "pinctrl-ep9312" },
+	{ /* sentinel */ }
+};

Since the strings are constants, gcc should even be able to deduplicate =
them.

>>=20
>> > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0dev_info(dev, "EP93xx So=
C revision %s\n", attrs->revision);
>>=20
>> Hmm... Is this message anyhow useful?
>>=20
>
> Can we keep it please ? It makes us happy when we see it in logs for
> historical reasons - it's been there since 2.4.

In general we don't do these at all, but since you are likely the only
person paying attention to this particular one, you may as well keep it.

     Arnd