From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>, barebox@lists.infradead.org
Subject: Re: do we need regmap-i2c in barebox?
Date: Wed, 3 Nov 2021 18:39:32 +0100 [thread overview]
Message-ID: <3fd5c873-525c-1ef0-3630-524e41afdccf@pengutronix.de> (raw)
In-Reply-To: <20211103203547.ee214b1d8bf7987970a3d904@gmail.com>
Hello Antony,
On 03.11.21 18:35, Antony Pavlov wrote:
> Hi!
>
> I have made draft version of pcf85363 i2c rtc driver for barebox.
> I used drivers/rtc/rtc-pcf85363.c from linux kernel as a prototype.
> The linux driver uses REGMAP_I2C linux feature. Barebox has regmap
> framework, but no special i2c regmap features.
There is d827f61e149b ("regmap: implement regmap_init_i2c")
since barebox v2021.07.0. What extra functionality are you missing?
>
> In barebox source tree I have found drivers/mfd/stpmic1.c which
> uses regmap for i2c device without REGMAP_I2C linux feature.
> So I have just stolen i2c regmap code from stpmic1.c for pcf85363
> driver. I'll send pcf85363 i2c rtc driver for barebox in a separate
> message.
>
> Is there any sense in porting drivers/base/regmap/regmap-i2c.c from
> linux into barebox?
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-11-03 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 17:35 Antony Pavlov
2021-11-03 17:39 ` Ahmad Fatoum [this message]
2021-11-03 17:54 ` Antony Pavlov
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=3fd5c873-525c-1ef0-3630-524e41afdccf@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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