public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	 Andreas Kemnade <andreas@kemnade.info>,
	 Kevin Hilman <khilman@baylibre.com>,
	 Roger Quadros <rogerq@kernel.org>,
	 Tony Lindgren <tony@atomide.com>,
	 Matthias Schiffer <matthias.schiffer@tq-group.com>,
	 linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ti-sysc: allow OMAP2 and OMAP4 timers to be reserved on AM33xx
Date: Fri, 06 Feb 2026 20:10:28 +0100	[thread overview]
Message-ID: <87pl6hpu1n.fsf@gnu.org> (raw)
In-Reply-To: <20250825131114.2206804-1-alexander.stein@ew.tq-group.com>


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

      parent reply	other threads:[~2026-02-06 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 13:11 [PATCH 1/1] ti-sysc: allow OMAP2 and OMAP4 timers to be reserved on AM33xx Alexander Stein
2025-11-04 23:06 ` Kevin Hilman
2026-02-06 19:10 ` Mathieu Othacehe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pl6hpu1n.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=andreas@kemnade.info \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matthias.schiffer@tq-group.com \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox