All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: 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: Tue, 14 Jan 2020 08:46:13 -0800	[thread overview]
Message-ID: <20200114164613.GR5885@atomide.com> (raw)
In-Reply-To: <52905C15-A2D1-4372-9781-D602D0B274B6@goldelico.com>

* H. Nikolaus Schaller <hns@goldelico.com> [200114 16:38]:
> Hi Tony,
> 
> > Am 14.01.2020 um 16:09 schrieb Tony Lindgren <tony@atomide.com>:
> > 
> > We are missing AESS for omap5. Looks like it's similar to what we have
> > for omap4, and this gets ti-sysc interconnect target module driver to
> > detect it properly.
> > 
> > Note that we currently have no child device driver available for it.
> 
> What I have is a non-working and no more compiling driver originally written by
> Peter Ujfalusi and reworked by Andrej Utkin. We did have it almost running on
> v4.14 or so except problems with firmware versions and headers...
> 
> There we used classical hwmods and I could revert them now to try your new patches.
> Unfortunately, I could only compile-test your two patches but nothing with AESS.
> 
> We had tried to follow kernel API changes in the sound subsystem but today it is
> not even compiling any more :(
> 
> So getting a working device driver is an even bigger task than SGX was.

OK. Well hopefully that's at least a little bit easier now though.

> > Cc: H. Nikolaus Schaller <hns@goldelico.com>
> > Cc: Matthijs van Duin <matthijsvanduin@gmail.com>
> > Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
> > Cc: Tero Kristo <t-kristo@ti.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> > ---
> > 
> > Note that this depends on "[PATCH] clk: ti: omap5: Add missing AESS clock".
> > 
> > arch/arm/boot/dts/omap5-l4-abe.dtsi | 16 ++++++++++++++--
> > 1 file changed, 14 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/boot/dts/omap5-l4-abe.dtsi b/arch/arm/boot/dts/omap5-l4-abe.dtsi
> > --- a/arch/arm/boot/dts/omap5-l4-abe.dtsi
> > +++ b/arch/arm/boot/dts/omap5-l4-abe.dtsi
> > @@ -426,8 +426,20 @@ target-module@c0000 {			/* 0x401c0000, ap 30 1e.0 */
> > 		};
> > 
> > 		target-module@f1000 {			/* 0x401f1000, ap 32 20.0 */
> 
> Here its may be good to have an "aess" label.

Care to clarify what you have in mind? The module is generic, aess
device will be the child node.

How about just a comment for aess?

Regards,

Tony


WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: "H. Nikolaus Schaller" <hns-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Benoît Cousson"
	<bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Matthijs van Duin"
	<matthijsvanduin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"Peter Ujfalusi" <peter.ujfalusi-l0cyMroinI0@public.gmane.org>,
	"Tero Kristo" <t-kristo-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH] ARM: dts: Configure omap5 AESS
Date: Tue, 14 Jan 2020 08:46:13 -0800	[thread overview]
Message-ID: <20200114164613.GR5885@atomide.com> (raw)
In-Reply-To: <52905C15-A2D1-4372-9781-D602D0B274B6-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>

* H. Nikolaus Schaller <hns-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org> [200114 16:38]:
> Hi Tony,
> 
> > Am 14.01.2020 um 16:09 schrieb Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>:
> > 
> > We are missing AESS for omap5. Looks like it's similar to what we have
> > for omap4, and this gets ti-sysc interconnect target module driver to
> > detect it properly.
> > 
> > Note that we currently have no child device driver available for it.
> 
> What I have is a non-working and no more compiling driver originally written by
> Peter Ujfalusi and reworked by Andrej Utkin. We did have it almost running on
> v4.14 or so except problems with firmware versions and headers...
> 
> There we used classical hwmods and I could revert them now to try your new patches.
> Unfortunately, I could only compile-test your two patches but nothing with AESS.
> 
> We had tried to follow kernel API changes in the sound subsystem but today it is
> not even compiling any more :(
> 
> So getting a working device driver is an even bigger task than SGX was.

OK. Well hopefully that's at least a little bit easier now though.

> > Cc: H. Nikolaus Schaller <hns-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
> > Cc: Matthijs van Duin <matthijsvanduin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Cc: Peter Ujfalusi <peter.ujfalusi-l0cyMroinI0@public.gmane.org>
> > Cc: Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org>
> > Signed-off-by: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
> > ---
> > 
> > Note that this depends on "[PATCH] clk: ti: omap5: Add missing AESS clock".
> > 
> > arch/arm/boot/dts/omap5-l4-abe.dtsi | 16 ++++++++++++++--
> > 1 file changed, 14 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/boot/dts/omap5-l4-abe.dtsi b/arch/arm/boot/dts/omap5-l4-abe.dtsi
> > --- a/arch/arm/boot/dts/omap5-l4-abe.dtsi
> > +++ b/arch/arm/boot/dts/omap5-l4-abe.dtsi
> > @@ -426,8 +426,20 @@ target-module@c0000 {			/* 0x401c0000, ap 30 1e.0 */
> > 		};
> > 
> > 		target-module@f1000 {			/* 0x401f1000, ap 32 20.0 */
> 
> Here its may be good to have an "aess" label.

Care to clarify what you have in mind? The module is generic, aess
device will be the child node.

How about just a comment for aess?

Regards,

Tony

  reply	other threads:[~2020-01-14 16:46 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 [this message]
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
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=20200114164613.GR5885@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=matthijsvanduin@gmail.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=t-kristo@ti.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.