Re: Pandaboard ES

[Rui-Xiang Guo <rxg%lavabit.com@localhost>]

On Tue, Apr 08, 2025 at 04:06:24PM -0400, Lwazi Dube wrote:
> >
> > > > Some known issues:
> > > > 1. a9ptmr manually obtains frequency, not sure if this is a good
> > solution.
> > > > 2. armpmu failed to be attached, it seems to be a problem with dts.
> > > > 3. ti_prcm doesn't support multiple instances so we can get the last
> > attached
> > > >    PRCM (CM2) clocks only, this causes tiwdt to not work.
> > >
> > > Issue 3 should be my misunderstanding, tiwdt is attached if I comment out
> > > wd_timer3 clock in omap4_prcm.
> >
> > Issue 1 is fixed by changing a9ptmr pass 2 to 3 so a9ptmr.diff is no need.
> >
> 
> I see this in your original dmesg: arma9ptmr0 at a9ptmr0: A9 Private Timer
> (349 MHz)
> Are the private timers still 349MHz after your change?

Hi,
it becomes
[   1.0000000] arma9ptmr0 at a9ptmr0: A9 Private Timer (174 MHz)
which comes from mpu_periphclk.

The updated boot log:
https://dmesgd.nycbug.org/index.cgi?do=view&id=8308

BTW, the cause of Issue 2 is the default loading omap4-panda.dtb has no
interrupts definition. I will try to force load omap4-panda-es.dtb.

-rxg