Re: I2C/IIC working on RPI4 8GB?

Mark Millard via freebsd-arm <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>

On 2021-May-2, at 03:14, Mark Murray <[email protected]> wrote:

> On 2 May 2021, at 03:58, Mark Millard <[email protected]> wrote:
>> 
>> [I was given a code hint that I've not investigated yet.]
>> 
>> But going in a different direction, based on my default
>> context on the local FreeBSD RPI4B 8 GiByte:
> 
> ... and a whole lot more really helpful diagnosis over several emails.
> 
> Thank you VERY much! it will take me a while to digest this, but digest it I will.
> 
> Ultimately, it would be good for a "make buildworld; make installworld" on an RPi to install the in-source FDT, and for it to be correct, such that it doesn't take some trickier port modification to have a working FDT. This is worth taking on as a project, but I won't get to it very soon.

When I collected and sent out boot -v gpio/i2c/iic information
(case independent) for my context, one of the things in it was
a "regfix0: Cannot set GPIO pin" notice with "REGNODE_INIT
failed" and "regfix0: Cannot register regulator" lines as well:

. . .
gpio0: set pin 53 to func 7, pull 2
gpio1: <Raspberry Pi Firmware GPIO controller> on bcm2835_firmware0
gpiobus1: <GPIO bus> on gpio1
regfix0: Cannot set GPIO pin: 6
REGNODE_INIT failed: 6
regfix0: Cannot register regulator.
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 13 on simplebus0
. . .

Do you get the same?

I wonder if it might interfere with part of the gpio*
initialization.

(I was testing a 2021-Mar-12 vintage of FreeBSD but with
more recent RPi* and u-boot materials.)

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.