Re: clk mess on omap4460 with mpu clock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

> Am 03.09.2024 um 14:36 schrieb Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>:
> 
> Hi Andreas,
> 
> On Tue, Sep 3, 2024 at 2:34 PM Andreas Kemnade <andreas@xxxxxxxxxxxx> wrote:
>> Am Mon, 2 Sep 2024 15:53:07 +0200
>> schrieb Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>:
>>> On Mon, Jun 3, 2024 at 11:41 PM Andreas Kemnade
>>> <andreas@xxxxxxxxxxxx> wrote:
>>>> just stumbled across this on 6.10-rc1:
>>>> 
>>>> [    1.475830] ocp:target-module@48210000:mpu:fck: device ID is
>>>> greater than 24 [    1.483154] ti-sysc ocp:target-module@48210000:
>>>> could not add child clock fck: -12

I just have my PandaES up and running today (with LetuxOS) and there I can't see
such a report with v6.11-rc6 and everything seems to be fine (except some certainly
unrelated  44000000.l3-noc:L3 Standard Error: MASTER MPU TARGET DSS (Read Link): At Address: 0x00006070 : Data Access in User mode during Functional access).

So can it be a spurious error in 6.10-rc1 and is already fixed (maybe as a side-effect)?
Or do we have a happy fix in our distribution kernel? Or does it depend on CONFIG?

I can roll back and try to build&run letux-6.10-rc1 as well.

BR,
Nikolaus






[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux