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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176229761651.2840692.2154178445405105304.b4-ty@baylibre.com>
Date: Tue, 04 Nov 2025 15:06:56 -0800
From: Kevin Hilman <khilman@...libre.com>
To: Aaro Koskinen <aaro.koskinen@....fi>, 
 Andreas Kemnade <andreas@...nade.info>, Roger Quadros <rogerq@...nel.org>, 
 Tony Lindgren <tony@...mide.com>, 
 Alexander Stein <alexander.stein@...tq-group.com>
Cc: 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


On Mon, 25 Aug 2025 15:11:13 +0200, Alexander Stein wrote:
> 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.
> 
> 

Applied, thanks!

[1/1] ti-sysc: allow OMAP2 and OMAP4 timers to be reserved on AM33xx
      commit: 3f61783920504b2cf99330b372d82914bb004d8e

Best regards,
-- 
Kevin Hilman <khilman@...libre.com>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ