All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org,
	"Matthijs van Duin" <matthijsvanduin@gmail.com>,
	"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
	"Tero Kristo" <t-kristo@ti.com>
Subject: Re: [PATCH] ARM: dts: Configure omap5 AESS
Date: Wed, 15 Jan 2020 13:49:52 +0100	[thread overview]
Message-ID: <5E0BF30D-2723-4724-89E1-449230758EE2@goldelico.com> (raw)
In-Reply-To: <20200114210039.GT5885@atomide.com>


> Am 14.01.2020 um 22:00 schrieb Tony Lindgren <tony@atomide.com>:
> 
> * H. Nikolaus Schaller <hns@goldelico.com> [200114 18:40]:
>> I have checked our tree and it is already built into a separate module with
>> 
>> sound/soc/ti/aess/omap-aess-core.c:	{ .compatible = "ti,omap4-aess", },
>> 
>> So
>> 
>>> target-module@f1000 {			/* 0x401f1000, ap 32 20.0 */
>>> 	...
>>> 	aess: aess {
>>> 		compatible = "ti,omap4-aess";
>>> 		status = "disabled";
>>> 	};
>>> };
>> 
>> would be what we will need.
> 
> OK good to hear.

I have cleaned up my working tree and added your patches and the one
above (without status = "disabled" and could
a) boot well
b) see that the (non-working) aess driver module is loaded through child node

So you can add my Tested-by: Nikolaus Schaller <hns@goldelico.com>

BR and thanks,
Nikolaus


  reply	other threads:[~2020-01-15 12:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 15:09 [PATCH] ARM: dts: Configure omap5 AESS Tony Lindgren
2020-01-14 16:37 ` H. Nikolaus Schaller
2020-01-14 16:46   ` Tony Lindgren
2020-01-14 16:46     ` Tony Lindgren
2020-01-14 17:04     ` H. Nikolaus Schaller
2020-01-14 17:16       ` Tony Lindgren
2020-01-14 17:16         ` Tony Lindgren
2020-01-14 18:29         ` H. Nikolaus Schaller
2020-01-14 18:29           ` H. Nikolaus Schaller
2020-01-14 18:39           ` H. Nikolaus Schaller
2020-01-14 18:39             ` H. Nikolaus Schaller
2020-01-14 21:00             ` Tony Lindgren
2020-01-14 21:00               ` Tony Lindgren
2020-01-15 12:49               ` H. Nikolaus Schaller [this message]
2020-01-16 18:52                 ` Tony Lindgren
2020-01-16 18:52                   ` Tony Lindgren
2020-01-16 15:53 ` kbuild test robot
2020-01-16 15:53   ` kbuild test robot
2020-01-16 15:53   ` kbuild test robot
2020-01-16 18:52   ` Tony Lindgren
2020-01-16 18:52     ` Tony Lindgren
2020-01-16 18:52     ` Tony Lindgren

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=5E0BF30D-2723-4724-89E1-449230758EE2@goldelico.com \
    --to=hns@goldelico.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matthijsvanduin@gmail.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=t-kristo@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.