Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Patrik Dahlström" <risca@dalakolonin.se>,
	letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
	linux-omap@vger.kernel.org
Subject: Re: ABE/AESS on modern kernel: clocks, hwmods etc.
Date: Sat, 2 Sep 2023 12:26:35 +0200	[thread overview]
Message-ID: <20230902122635.2482b0cf@aktux> (raw)
In-Reply-To: <CB775A6F-FDB6-4639-B386-8E8BEE4CD88C@goldelico.com>

On Sat, 2 Sep 2023 09:27:41 +0200
"H. Nikolaus Schaller" <hns@goldelico.com> wrote:

> Hi Tony,
> we are still struggling with ABE/AESS on the OMAP4/5 (PandaES, Pyra, OMAP5UEVM, BT-200).
> 
> Symptoms are that
> * pmem access will be broken after initializing the ABE-DSP
> * it seems the AES DSP is not running (and leads to timeouts when sending audio data to the buffers)
> * boot issues on BT-200
> 
> What we have found is that a TI kernel v3.8 works on the OMAP5EVM but newer kernels start to fail.
> 
> A major observation ist that hwmods have been removed in smaller pieces and the last removal
> was in v5.6: c33ff4c864d2b ARM: OMAP2+: Drop unused PRM defines for omap4
> 
> There are also some other unknown factors in our code where we do not know how to port to modern
> kernels:
> * there is a context lost code but how to make use of it?
> * pmem fails unless we disable omap_aess_write_event_generator(aess, EVENT_TIMER);
> 
> It seems as if clocks and code like omap_hwmod_aess_preprogram() is missing. Especially for the
> omap4 we have found no equivalent to aess_fclk which exists for omap5 and dra7.
> Nowhere is a reference using the abe_iclk node.
> 
for omap4 I guess the 
                        clocks = <&abe_clkctrl OMAP4_AESS_CLKCTRL 0>;

in omap4-l4-abe.dtsi should be enough and correcly referencing fclk?

Regards,
Andreas

  reply	other threads:[~2023-09-02 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53bc74ae-a2d5-40d5-8d51-bc0f062fcd15@email.android.com>
     [not found] ` <45F44D32-E846-4A53-BA20-9C78CD4411F3@goldelico.com>
     [not found]   ` <ZO4SWw/rbJH5Dpbq@dalakolonin.se>
     [not found]     ` <A029FB33-9FBB-4CE5-92D5-597E10B3A032@goldelico.com>
     [not found]       ` <ZPH5Yr3w7ruN/io0@dalakolonin.se>
     [not found]         ` <05B47ED4-CA2C-4754-ABB1-0591E9018E57@goldelico.com>
     [not found]           ` <ZPLYG16mwiwt9G9R@dalakolonin.se>
2023-09-02  7:27             ` ABE/AESS on modern kernel: clocks, hwmods etc H. Nikolaus Schaller
2023-09-02 10:26               ` Andreas Kemnade [this message]
2023-09-04  6:34                 ` Tony Lindgren
     [not found]                   ` <03375B42-C86E-4B37-98C2-C1FBA7AB68B6@goldelico.com>
2023-09-05  6:12                     ` Tony Lindgren
2023-09-05 12:42                       ` H. Nikolaus Schaller
2023-09-05 14:44                         ` Andreas Kemnade
2023-09-05 15:09                           ` H. Nikolaus Schaller
2023-09-05 15:48                             ` H. Nikolaus Schaller
2023-09-05 16:53                               ` H. Nikolaus Schaller
2023-09-06 13:50                         ` Patrik Dahlström

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=20230902122635.2482b0cf@aktux \
    --to=andreas@kemnade.info \
    --cc=hns@goldelico.com \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=risca@dalakolonin.se \
    --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