PandaBoard ES Boot

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

PandaBoard ES Boot

Aaron Bieber-2
Hola,

It seems there is an issue on the PandaBoard ES - it doesn't want to
display anything after booting the kernel:

cannot open sd0a:/etc/random.seed: No such file or directory
booting sd0a:/bsd: 2091172+7928680+435444 [64+297456+142800]=0xa659d0

Not sure if it needs to be told where the output should go, or what. I
tried doing a "set tty com0" which resulted in:

com0 not a console device

Any suggestions?

Cheers,
Aaron

Reply | Threaded
Open this post in threaded view
|

Re: PandaBoard ES Boot

Jonathan Gray-11
On Sat, Jul 16, 2016 at 07:44:17AM -0600, Aaron Bieber wrote:

> Hola,
>
> It seems there is an issue on the PandaBoard ES - it doesn't want to
> display anything after booting the kernel:
>
> cannot open sd0a:/etc/random.seed: No such file or directory
> booting sd0a:/bsd: 2091172+7928680+435444 [64+297456+142800]=0xa659d0
>
> Not sure if it needs to be told where the output should go, or what. I
> tried doing a "set tty com0" which resulted in:
>
> com0 not a console device
>
> Any suggestions?
>
> Cheers,
> Aaron
>

The console appears to be on 0x48020000 but the dtb does not
set stdout-path.

Try http://jsg.id.au/openbsd/omap4-panda-es.dtb

Index: Makefile
===================================================================
RCS file: /cvs/ports/sysutils/dtb/Makefile,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 Makefile
--- Makefile 29 May 2016 02:07:26 -0000 1.1.1.1
+++ Makefile 16 Jul 2016 14:03:11 -0000
@@ -2,6 +2,7 @@
 
 COMMENT= Device Tree Blobs
 DISTNAME= linux-4.6
+REVISION= 0
 PKGNAME= ${DISTNAME:S/linux/dtb/}
 CATEGORIES= sysutils
 HOMEPAGE= http://www.devicetree.org
--- /dev/null Sun Jul 17 00:20:30 2016
+++ patches/patch-arch_arm_boot_dts_imx6q-cm-fx6_dts Sun Jul 17 00:16:07 2016
@@ -0,0 +1,14 @@
+$OpenBSD$
+--- arch/arm/boot/dts/imx6q-cm-fx6.dts.orig Sun Jul 17 00:15:03 2016
++++ arch/arm/boot/dts/imx6q-cm-fx6.dts Sun Jul 17 00:15:38 2016
+@@ -22,6 +22,10 @@
+ reg = <0x10000000 0x80000000>;
+ };
+
++ chosen {
++ stdout-path = &uart4;
++ };
++
+ leds {
+ compatible = "gpio-leds";
+
--- /dev/null Sun Jul 17 00:20:44 2016
+++ patches/patch-arch_arm_boot_dts_omap4-panda-common_dtsi Sun Jul 17 00:18:52 2016
@@ -0,0 +1,14 @@
+$OpenBSD$
+--- arch/arm/boot/dts/omap4-panda-common.dtsi.orig Sun Jul 17 00:18:27 2016
++++ arch/arm/boot/dts/omap4-panda-common.dtsi Sun Jul 17 00:18:44 2016
+@@ -13,6 +13,10 @@
+ reg = <0x80000000 0x40000000>; /* 1 GB */
+ };
+
++ chosen {
++ stdout-path = &uart3;
++ };
++
+ aliases {
+ display0 = &dvi0;
+ display1 = &hdmi0;

Reply | Threaded
Open this post in threaded view
|

Re: PandaBoard ES Boot

Aaron Bieber-2
On Sun, Jul 17, 2016 at 12:24:34AM +1000, Jonathan Gray wrote:

> On Sat, Jul 16, 2016 at 07:44:17AM -0600, Aaron Bieber wrote:
> > Hola,
> >
> > It seems there is an issue on the PandaBoard ES - it doesn't want to
> > display anything after booting the kernel:
> >
> > cannot open sd0a:/etc/random.seed: No such file or directory
> > booting sd0a:/bsd: 2091172+7928680+435444 [64+297456+142800]=0xa659d0
> >
> > Not sure if it needs to be told where the output should go, or what. I
> > tried doing a "set tty com0" which resulted in:
> >
> > com0 not a console device
> >
> > Any suggestions?
> >
> > Cheers,
> > Aaron
> >
>
> The console appears to be on 0x48020000 but the dtb does not
> set stdout-path.
>
> Try http://jsg.id.au/openbsd/omap4-panda-es.dtb

This fixes the console issue, but now it's halting after this:

tiiic0 at simplebus0panic: prcm_v4_enablemodule: module not found
                                                                 
The operating system has halted.
Please press any key to reboot.


>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/sysutils/dtb/Makefile,v
> retrieving revision 1.1.1.1
> diff -u -p -r1.1.1.1 Makefile
> --- Makefile 29 May 2016 02:07:26 -0000 1.1.1.1
> +++ Makefile 16 Jul 2016 14:03:11 -0000
> @@ -2,6 +2,7 @@
>  
>  COMMENT= Device Tree Blobs
>  DISTNAME= linux-4.6
> +REVISION= 0
>  PKGNAME= ${DISTNAME:S/linux/dtb/}
>  CATEGORIES= sysutils
>  HOMEPAGE= http://www.devicetree.org
> --- /dev/null Sun Jul 17 00:20:30 2016
> +++ patches/patch-arch_arm_boot_dts_imx6q-cm-fx6_dts Sun Jul 17 00:16:07 2016
> @@ -0,0 +1,14 @@
> +$OpenBSD$
> +--- arch/arm/boot/dts/imx6q-cm-fx6.dts.orig Sun Jul 17 00:15:03 2016
> ++++ arch/arm/boot/dts/imx6q-cm-fx6.dts Sun Jul 17 00:15:38 2016
> +@@ -22,6 +22,10 @@
> + reg = <0x10000000 0x80000000>;
> + };
> +
> ++ chosen {
> ++ stdout-path = &uart4;
> ++ };
> ++
> + leds {
> + compatible = "gpio-leds";
> +
> --- /dev/null Sun Jul 17 00:20:44 2016
> +++ patches/patch-arch_arm_boot_dts_omap4-panda-common_dtsi Sun Jul 17 00:18:52 2016
> @@ -0,0 +1,14 @@
> +$OpenBSD$
> +--- arch/arm/boot/dts/omap4-panda-common.dtsi.orig Sun Jul 17 00:18:27 2016
> ++++ arch/arm/boot/dts/omap4-panda-common.dtsi Sun Jul 17 00:18:44 2016
> +@@ -13,6 +13,10 @@
> + reg = <0x80000000 0x40000000>; /* 1 GB */
> + };
> +
> ++ chosen {
> ++ stdout-path = &uart3;
> ++ };
> ++
> + aliases {
> + display0 = &dvi0;
> + display1 = &hdmi0;

Reply | Threaded
Open this post in threaded view
|

Re: PandaBoard ES Boot

Jonathan Gray-11
On Sun, Jul 17, 2016 at 07:42:49AM -0600, Aaron Bieber wrote:

> On Sun, Jul 17, 2016 at 12:24:34AM +1000, Jonathan Gray wrote:
> > On Sat, Jul 16, 2016 at 07:44:17AM -0600, Aaron Bieber wrote:
> > > Hola,
> > >
> > > It seems there is an issue on the PandaBoard ES - it doesn't want to
> > > display anything after booting the kernel:
> > >
> > > cannot open sd0a:/etc/random.seed: No such file or directory
> > > booting sd0a:/bsd: 2091172+7928680+435444 [64+297456+142800]=0xa659d0
> > >
> > > Not sure if it needs to be told where the output should go, or what. I
> > > tried doing a "set tty com0" which resulted in:
> > >
> > > com0 not a console device
> > >
> > > Any suggestions?
> > >
> > > Cheers,
> > > Aaron
> > >
> >
> > The console appears to be on 0x48020000 but the dtb does not
> > set stdout-path.
> >
> > Try http://jsg.id.au/openbsd/omap4-panda-es.dtb
>
> This fixes the console issue, but now it's halting after this:
>
> tiiic0 at simplebus0panic: prcm_v4_enablemodule: module not found
>                                                                  
> The operating system has halted.
> Please press any key to reboot.

Try the following.  The pins won't be explicitly muxed though
so it may not be enough.

http://jsg.id.au/openbsd/bsd

Index: prcm.c
===================================================================
RCS file: /cvs/src/sys/arch/armv7/omap/prcm.c,v
retrieving revision 1.10
diff -u -p -r1.10 prcm.c
--- prcm.c 17 Jul 2016 00:21:13 -0000 1.10
+++ prcm.c 17 Jul 2016 14:20:54 -0000
@@ -287,6 +287,12 @@ prcm_v3_bit(int mod)
  return PRCM_CLK_EN_GPIO5;
  case PRCM_GPIO5:
  return PRCM_CLK_EN_GPIO6;
+ case PRCM_I2C0:
+ return PRCM_CLK_EN_I2C1;
+ case PRCM_I2C1:
+ return PRCM_CLK_EN_I2C2;
+ case PRCM_I2C2:
+ return PRCM_CLK_EN_I2C3;
  default:
  panic("%s: module not found\n", __func__);
  }
@@ -414,6 +420,11 @@ prcm_v4_enablemodule(struct prcm_softc *
  case  PRCM_GPIO3:
  case  PRCM_GPIO4:
  case  PRCM_GPIO5:
+ /* XXX */
+ break;
+ case PRCM_I2C0:
+ case PRCM_I2C1:
+ case PRCM_I2C2:
  /* XXX */
  break;
  default:

Reply | Threaded
Open this post in threaded view
|

Re: PandaBoard ES Boot

Aaron Bieber-2


On Sun, Jul 17, 2016, at 08:24 AM, Jonathan Gray wrote:

> On Sun, Jul 17, 2016 at 07:42:49AM -0600, Aaron Bieber wrote:
> > On Sun, Jul 17, 2016 at 12:24:34AM +1000, Jonathan Gray wrote:
> > > On Sat, Jul 16, 2016 at 07:44:17AM -0600, Aaron Bieber wrote:
> > > > Hola,
> > > >
> > > > It seems there is an issue on the PandaBoard ES - it doesn't want to
> > > > display anything after booting the kernel:
> > > >
> > > > cannot open sd0a:/etc/random.seed: No such file or directory
> > > > booting sd0a:/bsd: 2091172+7928680+435444 [64+297456+142800]=0xa659d0
> > > >
> > > > Not sure if it needs to be told where the output should go, or what. I
> > > > tried doing a "set tty com0" which resulted in:
> > > >
> > > > com0 not a console device
> > > >
> > > > Any suggestions?
> > > >
> > > > Cheers,
> > > > Aaron
> > > >
> > >
> > > The console appears to be on 0x48020000 but the dtb does not
> > > set stdout-path.
> > >
> > > Try http://jsg.id.au/openbsd/omap4-panda-es.dtb
> >
> > This fixes the console issue, but now it's halting after this:
> >
> > tiiic0 at simplebus0panic: prcm_v4_enablemodule: module not found
> >                                                                  
> > The operating system has halted.
> > Please press any key to reboot.
>
> Try the following.  The pins won't be explicitly muxed though
> so it may not be enough.

Gets a bit further:

cannot open sd0a:/etc/random.seed: No such file or directory
booting sd0a:/bsd: 3720808+101120+486616 [64+496544+232356]=0x4d18d0

OpenBSD/armv7 booting ...
arg0 0x0 arg1 0xae7 arg2 0x88000000
Allocating page tables            
freestart = 0x807d2000, free_pages = 260142 (0x0003f82e)
IRQ stack: p0x80800000 v0xc0800000                      
ABT stack: p0x80801000 v0xc0801000
UND stack: p0x80802000 v0xc0802000
SVC stack: p0x80803000 v0xc0803000
Creating L1 page table at 0x807d4000
Mapping kernel                      
Constructing L2 page tables
undefined page pmap [ using 729336 bytes of bsd ELF symbol table ]
board type: 2791                                                  
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights
        reserved.
Copyright (c) 1995-2016 OpenBSD. All rights reserved.
http://www.OpenBSD.org
                                                                             
OpenBSD 6.0 (GENERIC) #103: Mon Jul 18 00:17:34 AEST 2016
    [hidden email]:/sys/arch/armv7/compile/GENERIC    
real mem  = 1073741824 (1024MB)                      
avail mem = 1044512768 (996MB)
warning: no entropy supplied by boot loader
mainbus0 at root: TI OMAP4 PandaBoard-ES  
cpu0 at mainbus0: ARM Cortex A9 R2 rev 10 (ARMv7 core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(32b/l,4way) I-cache, 32KB(32b/l,4way) wr-back D-cache      
cortex0 at mainbus0                                            
ampintc0 at cortex0 nirq 160
amptimer0 at cortex0: tick rate 396000 KHz
armliicc0 at cortex0: rtl 7 waymask: 0x0000000f
omap0 at mainbus0                              
omapid0 at omap0: omap4460
amptimer0: adjusting clock: new tick rate 350000 KHz
prcm0 at omap0 rev 0.0                              
omgpio0 at omap0: rev 0.1
gpio0 at omgpio0: 32 pins
omgpio1 at omap0: rev 0.1
gpio1 at omgpio1: 32 pins
omgpio2 at omap0: rev 0.1
gpio2 at omgpio2: 32 pins
omgpio3 at omap0: rev 0.1
gpio3 at omgpio3: 32 pins
omgpio4 at omap0: rev 0.1
gpio4 at omgpio4: 32 pins
omgpio5 at omap0: rev 0.1
gpio5 at omgpio5: 32 pins
ehci0 at omap0          
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "TI OMAP EHCI root hub" rev 2.00/1.00 addr 1
simplebus0 at mainbus0: "ocp"                            
simplebus1 at simplebus0: "l4"
simplebus2 at simplebus1: "scm"
simplebus3 at simplebus1: "scm"
simplebus4 at simplebus3: "omap4_padconf_global"
simplebus5 at simplebus1: "l4"                  
com0 at simplebus0: ti16750, 64 byte fifo
com0: probed fifo depth: 0 bytes        
com1 at simplebus0: ti16750, 64 byte fifo
com1: probed fifo depth: 0 bytes        
com2 at simplebus0: ti16750, 64 byte fifo
com2: console                            
com3 at simplebus0: ti16750, 64 byte fifo
com3: probed fifo depth: 0 bytes        
tiiic0 at simplebus0 rev 0.11  
iic0 at tiiic0              
"ti,twl6030" at iic0 addr 0x48 not configured
"ti,twl6040" at iic0 addr 0x4b not configured
tiiic1 at simplebus0 rev 0.11                
iic1 at tiiic1              
tiiic2 at simplebus0 rev 0.11
iic2 at tiiic2              
"ti,eeprom" at iic2 addr 0x50 not configured
tiiic3 at simplebus0panic: prcm_v4_enablemodule: module not found
                                                                 
Stopped at      $d:     ldrb    r15, [r15, r15, ror r15]!
   TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*    0      0      0     0x10000      0x200    0  swapper
panic+0x18                                              
        scp=0xc03c4568 rlv=0xc06059f8 (prcm_v4_enablemodule+0x28)
        rsp=0xc0804b5c rfp=0xc0804b70                            
prcm_v4_enablemodule+0x10            
        scp=0xc06059e0 rlv=0xc0605a80 (prcm_enablemodule+0x30)
        rsp=0xc0804b74 rfp=0xc0804b84                        
        r4=0xc0804b8c                
prcm_enablemodule+0x10
        scp=0xc0605a60 rlv=0xc0607dd8 (ti_iic_attach+0x120)
        rsp=0xc0804b88 rfp=0xc0804c48                      
ti_iic_attach+0xc                    
        scp=0xc0607cc4 rlv=0xc03b99d8 (config_attach+0x1d4)
        rsp=0xc0804c4c rfp=0xc0804c84                      
        r10=0x00000000 r9=0xc0804c88 r8=0xc06f1ef0 r7=0xc53be900
        r6=0xc06a2fa4 r5=0xc53db614 r4=0xc53db600              
config_attach+0xc                                
        scp=0xc03b9810 rlv=0xc053254c (simplebus_attach_node+0x114)
        rsp=0xc0804c88 rfp=0xc0804d58                              
        r10=0xc0804c88 r9=0xc0804ddc r8=0xc06a8afc r7=0xc53be900
        r6=0x00009d40 r5=0x0000000c r4=0xc53bc480              
simplebus_attach_node+0x10                      
        scp=0xc0532448 rlv=0xc05326c0 (simplebus_attach+0xb8)
        rsp=0xc0804d5c rfp=0xc0804d9c                        
        r10=0x00000000 r8=0xc06f1ef0 r7=0xc06a8afc r6=0xc0804d5c
        r5=0xc53be900 r4=0x00009d40                            
simplebus_attach+0xc              
        scp=0xc0532614 rlv=0xc03b99d8 (config_attach+0x1d4)
        rsp=0xc0804da0 rfp=0xc0804dd8                      
        r7=0xc53dd080 r6=0xc0698578 r5=0xc53be914 r4=0xc53be900
config_attach+0xc                                              
        scp=0xc03b9810 rlv=0xc053228c (mainbus_attach_node+0xe0)
        rsp=0xc0804ddc rfp=0xc0804eb0                          
        r10=0x000007c8 r9=0xc06a8afc r8=0xc53dd080 r7=0x00000001
        r6=0x00000001 r5=0xc0698818 r4=0xc0804ddc              
mainbus_attach_node+0x10                        
        scp=0xc05321bc rlv=0xc05323dc (mainbus_attach+0x12c)
        rsp=0xc0804eb4 rfp=0xc0804f58                      
        r10=0x00000000 r9=0x00000000 r8=0xc06a8afc r7=0x00000048
        r6=0xc0804eb4 r5=0xc53dd080 r4=0x000007c8              
mainbus_attach+0x10                              
        scp=0xc05322c0 rlv=0xc03b99d8 (config_attach+0x1d4)
        rsp=0xc0804f5c rfp=0xc0804f94                      
        r8=0xc06f1ef0 r7=0x00000000 r6=0xc0698510 r5=0xc53dd094
        r4=0xc53dd080                                          
config_attach+0xc    
        scp=0xc03b9810 rlv=0xc054477c (cpu_configure+0x20)
        rsp=0xc0804f98 rfp=0xc0804fa8                    
        r10=0xc06ed224 r9=0xc06ef3f0 r8=0xc06ed078 r7=0xc06ed3b4
        r6=0x00000000 r5=0xc06ecfdc r4=0xc071cd38              
cpu_configure+0xc                                
        scp=0xc0544768 rlv=0xc0397da4 (main+0x324)
        rsp=0xc0804fac rfp=0xc0804fec            
main+0xc                            
        scp=0xc0397a8c rlv=0xc0300164 (kernel_text+0x50)
        rsp=0xc0804ff0 rfp=0xc0804ffc                  
        r10=0xbef46ff0 r9=0x80000000 r8=0xc071cd38 r7=0x00000ae7
        r6=0x88000000 r5=0x00000ae7 r4=0x80300104              
kernel_text+0x4c                                
        scp=0xc0300160 rlv=0xc0540980 (mtx_leave+0x50)
        rsp=0xc0805000 rfp=0x00000000                
http://www.openbsd.org/ddb.html describes the minimum info required in
bug
reports.  Insufficient info makes it difficult to find and fix bugs.    
ddb>

>
> http://jsg.id.au/openbsd/bsd
>
> Index: prcm.c
> ===================================================================
> RCS file: /cvs/src/sys/arch/armv7/omap/prcm.c,v
> retrieving revision 1.10
> diff -u -p -r1.10 prcm.c
> --- prcm.c      17 Jul 2016 00:21:13 -0000      1.10
> +++ prcm.c      17 Jul 2016 14:20:54 -0000
> @@ -287,6 +287,12 @@ prcm_v3_bit(int mod)
>   return PRCM_CLK_EN_GPIO5;
>   case PRCM_GPIO5:
>   return PRCM_CLK_EN_GPIO6;
> +       case PRCM_I2C0:
> +               return PRCM_CLK_EN_I2C1;
> +       case PRCM_I2C1:
> +               return PRCM_CLK_EN_I2C2;
> +       case PRCM_I2C2:
> +               return PRCM_CLK_EN_I2C3;
>   default:
>   panic("%s: module not found\n", __func__);
>   }
> @@ -414,6 +420,11 @@ prcm_v4_enablemodule(struct prcm_softc *
>   case  PRCM_GPIO3:
>   case  PRCM_GPIO4:
>   case  PRCM_GPIO5:
> +                       /* XXX */
> +                       break;
> +               case PRCM_I2C0:
> +               case PRCM_I2C1:
> +               case PRCM_I2C2:
>   /* XXX */
>   break;
>   default:
>

Reply | Threaded
Open this post in threaded view
|

Re: PandaBoard ES Boot

Jonathan Gray-11
On Sun, Jul 17, 2016 at 10:41:22AM -0600, Aaron Bieber wrote:

>
>
> On Sun, Jul 17, 2016, at 08:24 AM, Jonathan Gray wrote:
> > On Sun, Jul 17, 2016 at 07:42:49AM -0600, Aaron Bieber wrote:
> > > On Sun, Jul 17, 2016 at 12:24:34AM +1000, Jonathan Gray wrote:
> > > > On Sat, Jul 16, 2016 at 07:44:17AM -0600, Aaron Bieber wrote:
> > > > > Hola,
> > > > >
> > > > > It seems there is an issue on the PandaBoard ES - it doesn't want to
> > > > > display anything after booting the kernel:
> > > > >
> > > > > cannot open sd0a:/etc/random.seed: No such file or directory
> > > > > booting sd0a:/bsd: 2091172+7928680+435444 [64+297456+142800]=0xa659d0
> > > > >
> > > > > Not sure if it needs to be told where the output should go, or what. I
> > > > > tried doing a "set tty com0" which resulted in:
> > > > >
> > > > > com0 not a console device
> > > > >
> > > > > Any suggestions?
> > > > >
> > > > > Cheers,
> > > > > Aaron
> > > > >
> > > >
> > > > The console appears to be on 0x48020000 but the dtb does not
> > > > set stdout-path.
> > > >
> > > > Try http://jsg.id.au/openbsd/omap4-panda-es.dtb
> > >
> > > This fixes the console issue, but now it's halting after this:
> > >
> > > tiiic0 at simplebus0panic: prcm_v4_enablemodule: module not found
> > >                                                                  
> > > The operating system has halted.
> > > Please press any key to reboot.
> >
> > Try the following.  The pins won't be explicitly muxed though
> > so it may not be enough.
>
> Gets a bit further:

Ah OMAP4 has an extra i2c unit.  Try this

http://jsg.id.au/openbsd/bsd

Index: prcm.c
===================================================================
RCS file: /cvs/src/sys/arch/armv7/omap/prcm.c,v
retrieving revision 1.10
diff -u -p -r1.10 prcm.c
--- prcm.c 17 Jul 2016 00:21:13 -0000 1.10
+++ prcm.c 17 Jul 2016 22:32:34 -0000
@@ -287,6 +287,12 @@ prcm_v3_bit(int mod)
  return PRCM_CLK_EN_GPIO5;
  case PRCM_GPIO5:
  return PRCM_CLK_EN_GPIO6;
+ case PRCM_I2C0:
+ return PRCM_CLK_EN_I2C1;
+ case PRCM_I2C1:
+ return PRCM_CLK_EN_I2C2;
+ case PRCM_I2C2:
+ return PRCM_CLK_EN_I2C3;
  default:
  panic("%s: module not found\n", __func__);
  }
@@ -414,6 +420,12 @@ prcm_v4_enablemodule(struct prcm_softc *
  case  PRCM_GPIO3:
  case  PRCM_GPIO4:
  case  PRCM_GPIO5:
+ /* XXX */
+ break;
+ case PRCM_I2C0:
+ case PRCM_I2C1:
+ case PRCM_I2C2:
+ case PRCM_I2C3:
  /* XXX */
  break;
  default:
Index: prcmvar.h
===================================================================
RCS file: /cvs/src/sys/arch/armv7/omap/prcmvar.h,v
retrieving revision 1.5
diff -u -p -r1.5 prcmvar.h
--- prcmvar.h 18 Mar 2014 07:34:17 -0000 1.5
+++ prcmvar.h 17 Jul 2016 22:32:34 -0000
@@ -51,6 +51,7 @@ enum PRCM_MODULES {
  PRCM_I2C0,
  PRCM_I2C1,
  PRCM_I2C2,
+ PRCM_I2C3,
 };
 
 #define PRCM_REG_MAX 6