[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdU=o0MzQUoEs5-HrEVP-snXN-hUef1K3U8Ppj18P6HVCg@mail.gmail.com>
Date: Thu, 17 Oct 2024 12:51:26 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: mturquette@...libre.com, sboyd@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, alexandre.belloni@...tlin.com,
magnus.damm@...il.com, p.zabel@...gutronix.de,
linux-renesas-soc@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rtc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v3 06/12] rtc: renesas-rtca3: Add driver for RTCA-3
available on Renesas RZ/G3S SoC
Hi Wolfram,
On Thu, Oct 17, 2024 at 12:45 PM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
> sorry for being late to the game. I just noticed this series and
> wonder...
> ... if it has been considered to expand the existing rtc-sh driver? The
> register set looks identical up to RMONAR. From that on, it looks a
> different. Maybe the different offsets and bit positions could be
> abstracted away by some sh_rtc_{read|write} helper? Or is there some
> other new handling which makes re-using rtc-sh cumbersome?
Yes it has ;-)
https://lore.kernel.org/linux-renesas-soc/1c733190-bd46-43d0-8f3d-62e0ed5fde42@tuxon.dev
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists