[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8ffabc0d-73ca-27c6-5244-95e29901c60a@alliedtelesis.co.nz>
Date: Tue, 14 Feb 2023 22:36:51 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
CC: Ibrahim Tilki <Ibrahim.Tilki@...log.com>,
"a.zummo@...ertech.it" <a.zummo@...ertech.it>,
"jdelvare@...e.com" <jdelvare@...e.com>,
"linux@...ck-us.net" <linux@...ck-us.net>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Zeynep Arslanbenzer <Zeynep.Arslanbenzer@...log.com>
Subject: Re: [PATCH v3 1/2] drivers: rtc: add max313xx series rtc driver
On 15/02/23 10:40, Alexandre Belloni wrote:
> On 14/02/2023 20:28:05+0000, Chris Packham wrote:
>> Hi Ibrahim,
>>
>> On 9/11/22 01:22, Ibrahim Tilki wrote:
>>> Adding support for Analog Devices MAX313XX series RTCs.
>>>
>>> Signed-off-by: Ibrahim Tilki <Ibrahim.Tilki@...log.com>
>>> Signed-off-by: Zeynep Arslanbenzer <Zeynep.Arslanbenzer@...log.com>
>>> ---
>>> drivers/rtc/Kconfig | 11 +
>>> drivers/rtc/Makefile | 1 +
>>> drivers/rtc/rtc-max313xx.c | 1070 ++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 1082 insertions(+)
>>> create mode 100644 drivers/rtc/rtc-max313xx.c
>> What is the current state of this work? I see there are some comments on
>> this v3 iteration from late last year and I couldn't find any newer
>> iteration on any mailing list. We've got some new hardware arriving soon
>> that will have the MAX31331 RTC and I'm keen to see this patch series
>> land. Is there anything I can do to help it along? I can't be very
>> specific about when I'll see the new hardware (who can these days), the
>> last update was "boards are due in March".
>>
>> For the maintainers on the Cc list once the dust settles how would I get
>> this supported in a LTS kernel (we're currently using the 5.15 series)?
>> Or is totally out of the question because it's not just a new device id?
> This will not happen, you will have to update to the next LTS (which you
> should do anyway)
I was afraid that was going to be the answer. We'll have to carry it as
a local patch until there is a LTS version with the driver support we
need in it.
Powered by blists - more mailing lists