[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <44c969a1-8dda-425b-acf3-9a80dfa60e79@app.fastmail.com>
Date: Sun, 04 Jun 2023 19:19:22 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Andy Shevchenko" <andy.shevchenko@...il.com>,
"Nikita Shubin" <nikita.shubin@...uefel.me>
Cc: "Alexander Sverdlin" <alexander.sverdlin@...il.com>,
"Linus Walleij" <linus.walleij@...aro.org>,
"Daniel Lezcano" <daniel.lezcano@...aro.org>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Michael Peters" <mpeters@...eddedts.com>,
"Kris Bahnsen" <kris@...eddedts.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 09/43] clocksource: ep93xx: Add driver for Cirrus Logic EP93xx
On Sat, Jun 3, 2023, at 22:06, andy.shevchenko@...il.com wrote:
> Thu, Jun 01, 2023 at 08:34:00AM +0300, Nikita Shubin kirjoitti:
>> This us a rewrite of EP93xx timer driver in
>> arch/arm/mach-ep93xx/timer-ep93xx.c trying to do everything
>> the device tree way:
>>
>> - Make every IO-access relative to a base address and dynamic
>> so we can do a dynamic ioremap and get going.
>> - Find register range and interrupt from the device tree.
>
> ...
>
>> +config EP93XX_TIMER
>> + bool "Cirrus Logic ep93xx timer driver" if COMPILE_TEST
>
> This is strange. What do you gain with this "if COMPILE_TEST"?
This ensures the driver is compiled in an x86 allmodconfig,
like most other clocksource drivers, but it's hidden on
all other configs without EP93xx support.
As long as the platform selects it, this is the normal
way to add a clocksource driver.
Arnd
Powered by blists - more mailing lists