From: Juergen Borleis <jbe@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>,
Andreas Kemnade <andreas@kemnade.info>
Cc: barebox@lists.infradead.org
Subject: Re: rn5t618 vs. rn5t568
Date: Tue, 02 May 2023 10:37:08 +0200 [thread overview]
Message-ID: <9230126707a1938c0dee22efa0b3fbaab0098c7e.camel@pengutronix.de> (raw)
In-Reply-To: <20230427073630.GT13543@pengutronix.de>
Hi,
Am Donnerstag, dem 27.04.2023 um 09:36 +0200 schrieb Sascha Hauer:
> On Wed, Apr 26, 2023 at 09:09:36PM +0200, Andreas Kemnade wrote:
> > Hi,
> >
> > just looked a bit around in the source and stumbled across drivers/mfd/rn5t568.c
> >
> > It contains
> > * MFD core driver for Ricoh RN5T618 PMIC
> >
> > but the filename is rn5t568.c That is very confusing.
> > a compatible ricoh,rn5t568 (but 567) does not exist in the kernel.
567 and 568 are pin compatible. As far as I know the 568 has some fixed OTP
settings which are used after reset. Depending on the type extension (C, S, AD…)
the I²C address differs and the default output voltages.
> > So which chip this is really about? Did not analyse things deeper yet.
> >
> > I am also curious because I wrote most stuff in the kernel about the rn5t618/rc5t619.
>
> Jürgen had to support the rn5t568 which is not yet supported in Linux.
> He took the Kernel rn5t618.c driver and adjusted it accordingly. Jürgen
> can't remember exactly, but he said the chips are quite similar.
Due to the support of the 567 variant it is already supported in the kernel.
jb
--
Pengutronix e.K. | Juergen Borleis |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-128 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
next prev parent reply other threads:[~2023-05-02 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 19:09 Andreas Kemnade
2023-04-27 7:36 ` Sascha Hauer
2023-05-02 8:37 ` Juergen Borleis [this message]
2023-05-04 7:10 ` Andreas Kemnade
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=9230126707a1938c0dee22efa0b3fbaab0098c7e.camel@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=andreas@kemnade.info \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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