Sorry to have posted this here, i found somebody else having that problem
on D1 and figured it might be some error in the dtsi - as it is missing
pindefs.
Only thing missing above was the pinctrl-names in the i2c0 node.
pinctrl-names = "default";
Jakob L schrieb am Montag, 29. Januar 2024 um 13:01:20 UTC+1:
> Hi!
> I am now having issues with i2c on T113. The pin nodes were added to
> sunxi-d1s-t113.dts. They are not there by default.
>
> --- a/arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi
> +++ b/arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi
> @@ -52,6 +52,11 @@ pio: pinctrl@2000000 {
> #gpio-cells = <3>;
> #interrupt-cells = <3>;
>
> + i2c0_pins: i2c0-pins {
> + pins = "PB3", "PB2";
> + function = "i2c0";
> + };
> +
> /omit-if-no-ref/
> can0_pins: can0-pins {
> pins = "PB2", "PB3";
>
> and added i2c0 to my dts.
>
> +&i2c0 {
> + pinctrl-0 = <&i2c0_pins>;
> + clock-frequency = <400000>;
> + status = "okay";
> +};
>
> There are pullups on the board and the lines are actually pulled up to
> 3.3V.
> But the i2cdetect command results in faulure. With connected i2c-slave and
> without.
> Error message is: mv64xxx: I2C bus locked, block: 1
>
> pinctrl-sun20i-d1.c does have the correct definitions. So that should be
> fine.
> I also tried pins = "PB3", "PB2", because i think in other dtsi the first
> pin is SCL.
>
> Anyone has a working i2c on this chip?
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/linux-sunxi/660f85f7-6f0f-4d9f-b81c-1ef7c8dcbf6fn%40googlegroups.com.
