linux-kernel - Re: [PATCH 1/1] ti-sysc: allow OMAP2 and OMAP4 timers to be reserved on AM33xx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87pl6hpu1n.fsf@gnu.org>
Date: Fri, 06 Feb 2026 20:10:28 +0100
From: Mathieu Othacehe <othacehe@....org>
To: Alexander Stein <alexander.stein@...tq-group.com>
Cc: Aaro Koskinen <aaro.koskinen@....fi>,  Andreas Kemnade
 <andreas@...nade.info>,  Kevin Hilman <khilman@...libre.com>,  Roger
 Quadros <rogerq@...nel.org>,  Tony Lindgren <tony@...mide.com>,  Matthias
 Schiffer <matthias.schiffer@...group.com>,  linux-omap@...r.kernel.org,
  linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ti-sysc: allow OMAP2 and OMAP4 timers to be
 reserved on AM33xx


Hello,

> am33xx.dtsi has the same clock setup as am35xx.dtsi, setting
> ti,no-reset-on-init and ti,no-idle on timer1_target and timer2_target,
> so AM33 needs the same workaround as AM35 to avoid ti-sysc probe
> failing on certain target modules.

On am335 (Linux 6.12.66), this commit has solved those two errors:

[ 0.882765] ti-sysc: probe of 44e31000.target-module failed with error -16
[ 0.973457] ti-sysc: probe of 48040000.target-module failed with error -16

but has in turn introduced those two:

[ 2.149708] ti-sysc 44e31000.target-module: Failed to create device link (0x180) with ocp
[ 2.149735] ti-sysc 48040000.target-module: Failed to create device link (0x180) with ocp

Any idea how to fix those?

Thanks,

Mathieu