linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: "Tony Lindgren" <tony@atomide.com>,
	"Andreas Kemnade" <andreas@kemnade.info>,
	"Patrik Dahlström" <risca@dalakolonin.se>,
	peter.ujfalusi@gmail.com
Cc: letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
	linux-omap@vger.kernel.org,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: [RFC 0/6] tentative additions to fix ABE/AESS device tree entries for OMAP4&5
Date: Tue,  5 Sep 2023 14:50:09 +0200	[thread overview]
Message-ID: <cover.1693918214.git.hns@goldelico.com> (raw)

RFC V1 2023-09-05 14:50:14:
RFC: tentative additions to fix ABE/AESS device tree entries

This is part of a bigger project to provide a modern driver for the
OMAP4/5 Audio Engine (ABE/AE/AESS). The first step is to fix/add some
device tree records so that this allows to do power and clock management
by a driver and give the processor access to all interface registers
and memory blocks.

Main RFC question is if clock setup is correct. For example there is
no connection to abe_giclk_div / ocp_abe_iclk / abe_iclk.

Notes:
- this may be extensible to DRA7xx
- code is based on v6.5
- there is no bindings document for ti,omap4-aess

H. Nikolaus Schaller (4):
  ARM: DTS: omap5-l4-abe: we do not need separate target-modules for
    dmem, cmem, smem
  ARM: DTS: omap5-l4-abe: add an aess (audio DSP of OMAP4 and OMAP5)
    child
  ARM: DTS: omap4-l4-abe: add an aess (audio DSP of OMAP4 and OMAP5)
    child
  ARM: DTS: omap4-panda-common: enable aess, add phandles for aess and
    mcbsp1/2/3

Marek Belisko (1):
  ARM: DTS: omap5-board-common: enable aess, add phandles for aess and
    mcbsp1/2/3

Peter Ujfalusi (1):
  ARM: DTS: omap4-l4-abe: Add McASP configuration

 arch/arm/boot/dts/ti/omap/omap4-l4-abe.dtsi   | 78 +++++++++++----
 .../boot/dts/ti/omap/omap4-panda-common.dtsi  | 22 ++++-
 .../boot/dts/ti/omap/omap5-board-common.dtsi  | 15 +++
 arch/arm/boot/dts/ti/omap/omap5-l4-abe.dtsi   | 98 +++++++++++--------
 4 files changed, 149 insertions(+), 64 deletions(-)

-- 
2.42.0


             reply	other threads:[~2023-09-05 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 12:50 H. Nikolaus Schaller [this message]
2023-09-05 12:50 ` [RFC 1/6] ARM: DTS: omap5-l4-abe: we do not need separate target-modules for dmem, cmem, smem H. Nikolaus Schaller
2023-09-05 12:50 ` [RFC 2/6] ARM: DTS: omap5-l4-abe: add an aess (audio DSP of OMAP4 and OMAP5) child H. Nikolaus Schaller
2023-09-05 12:50 ` [RFC 3/6] ARM: DTS: omap5-board-common: enable aess, add phandles for aess and mcbsp1/2/3 H. Nikolaus Schaller
2023-09-05 12:50 ` [RFC 4/6] ARM: DTS: omap4-l4-abe: Add McASP configuration H. Nikolaus Schaller
2023-09-07  5:35   ` Tony Lindgren
2023-09-05 12:50 ` [RFC 5/6] ARM: DTS: omap4-l4-abe: add an aess (audio DSP of OMAP4 and OMAP5) child H. Nikolaus Schaller
2023-09-07  5:29   ` Tony Lindgren
2023-09-05 12:50 ` [RFC 6/6] ARM: DTS: omap4-panda-common: enable aess, add phandles for aess and mcbsp1/2/3 H. Nikolaus Schaller

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=cover.1693918214.git.hns@goldelico.com \
    --to=hns@goldelico.com \
    --cc=andreas@kemnade.info \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).