mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <>
Cc: Ahmad Fatoum <>
Subject: do we need regmap-i2c in barebox?
Date: Wed, 3 Nov 2021 20:35:47 +0300	[thread overview]
Message-ID: <> (raw)


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.

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

Is there any sense in porting drivers/base/regmap/regmap-i2c.c from
linux into barebox?

Best regards,
  Antony Pavlov

barebox mailing list

             reply	other threads:[~2021-11-03 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 17:35 Antony Pavlov [this message]
2021-11-03 17:39 ` Ahmad Fatoum
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:

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

  git send-email \ \ \ \ \

* 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