From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: frank-w@public-files.de, barebox@lists.infradead.org
Subject: Re: Driver load order
Date: Thu, 19 May 2022 14:17:58 +0200 [thread overview]
Message-ID: <1f4f9e12-34f9-6bf2-d15d-1ccf8c7e9329@pengutronix.de> (raw)
In-Reply-To: <1694C0B0-A962-420E-BA70-8061E8E9CA7F@public-files.de>
Hello Frank,
On 19.05.22 12:59, Frank Wunderlich wrote:
> Hi,
>
> I try to create a basic driver for rk808 pmic/iodomains. I've noticed that first the iodomain driver is probed and then the rk808 on,but i need it reversed as rk808 registers regulators linked in iodomain via devicetree.
>
> How can i defer iodomain probing till rk808 is ready (regulators available defined as phandles in iodomain dt node)? Currently i get always ENODEV (property does not exist or regulator is not ready yet)....
>
> This is my current (dirty) source:
> https://github.com/frank-w/barebox-r2pro/commits/r2pro-iodomain
While I don't know what iodomains are, I had ported the rk808 driver to barebox for
use with the Rock Pi N10. I haven't come around to upstream it, because I haven't
figured out why I can't use the existing regmap helpers like Linux does.
I have sent you the patches as a reply to your mail. Perhaps they'll
save you some effort.
Cheers,
Ahmad
> regards Frank
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/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:[~2022-05-19 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:59 Frank Wunderlich
2022-05-19 11:54 ` Sascha Hauer
2022-05-19 12:43 ` Aw: " Frank Wunderlich
2022-05-19 12:50 ` Ahmad Fatoum
2022-05-19 13:10 ` Sascha Hauer
2022-05-19 17:54 ` Aw: " Frank Wunderlich
2022-05-21 10:31 ` Frank Wunderlich
2022-05-24 8:53 ` Ahmad Fatoum
2022-05-24 9:13 ` Aw: " Frank Wunderlich
2022-05-24 9:21 ` Ahmad Fatoum
2022-05-19 12:10 ` [PATCH 1/2] regmap: implement regmap_init_i2c_smbus Ahmad Fatoum
2022-05-19 12:10 ` [PATCH 2/2] regulator: add Rockchip rk808 support Ahmad Fatoum
2022-05-19 12:17 ` Ahmad Fatoum [this message]
2022-05-19 12:42 ` Driver load order Ahmad Fatoum
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=1f4f9e12-34f9-6bf2-d15d-1ccf8c7e9329@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=frank-w@public-files.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