linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "Tilki, Ibrahim" <Ibrahim.Tilki@analog.com>,
	"a.zummo@towertech.it" <a.zummo@towertech.it>,
	"jdelvare@suse.com" <jdelvare@suse.com>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Arslanbenzer, Zeynep" <Zeynep.Arslanbenzer@analog.com>
Subject: Re: [PATCH v3 1/2] drivers: rtc: add max313xx series rtc driver
Date: Mon, 13 Mar 2023 03:20:17 +0100	[thread overview]
Message-ID: <20230313022017afe9a8fe@mail.local> (raw)
In-Reply-To: <52382400-5abd-b473-6cf7-333e7deab2d4@alliedtelesis.co.nz>

Hello,

On 13/03/2023 02:15:26+0000, Chris Packham wrote:
> Hi Ibrahim,
> 
> On 18/02/23 04:17, Tilki, Ibrahim 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@analog.com>
> >>> Signed-off-by: Zeynep Arslanbenzer <Zeynep.Arslanbenzer@analog.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?
> > Hi Chris,
> >
> > Patch v4 is on the way, I will be sending it in a few weeks.
> > It is hard to tell when it is going to land but I expect to be more responsive
> > to reviews after patch v4.
> 
> FYI I've now got some boards with a MAX31331. I've given v3 a quick test 
> and it works for me.
> 
> Are you also looking at a u-boot driver? If not I can port your driver 
> across reasonably easily.
> 

I'm curious why would you need an RTC driver for u-boot?


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2023-03-13  2:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 12:22 [PATCH v3 0/2] drivers: rtc: add max313xx series rtc driver Ibrahim Tilki
2022-11-08 12:22 ` [PATCH v3 1/2] " Ibrahim Tilki
2022-11-08 12:57   ` Christophe JAILLET
2022-11-08 13:27   ` Guenter Roeck
2022-12-10 22:01   ` Alexandre Belloni
2023-02-14 20:28   ` Chris Packham
2023-02-14 21:40     ` Alexandre Belloni
2023-02-14 22:36       ` Chris Packham
2023-02-17 15:17     ` Tilki, Ibrahim
2023-02-19 20:19       ` Chris Packham
2023-03-13  2:15       ` Chris Packham
2023-03-13  2:20         ` Alexandre Belloni [this message]
2023-03-13  2:30           ` Chris Packham
2022-11-08 12:22 ` [PATCH v3 2/2] dt-bindings: rtc: add max313xx RTCs Ibrahim Tilki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230313022017afe9a8fe@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=Ibrahim.Tilki@analog.com \
    --cc=Zeynep.Arslanbenzer@analog.com \
    --cc=a.zummo@towertech.it \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).