From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Roger Quadros <rogerq@ti.com>, Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 06/12] ARM: dts: am335x-bone-common: Enable PRU-ICSS interconnect node
Date: Wed, 26 Feb 2020 14:39:21 -0800 [thread overview]
Message-ID: <20200226223921.GB37466@atomide.com> (raw)
In-Reply-To: <20200226223745.GA37466@atomide.com>
* Tony Lindgren <tony@atomide.com> [200226 22:38]:
> * Suman Anna <s-anna@ti.com> [200226 20:35]:
> > On 2/26/20 12:29 PM, Tony Lindgren wrote:
> > > * Suman Anna <s-anna@ti.com> [200225 20:47]:
> > >> The PRU-ICSS target module node was left in disabled state in the base
> > >> am33xx-l4.dtsi file. Enable this node on all the AM335x beaglebone
> > >> boards as they mostly use a AM3358 or a AM3359 SoC which do contain
> > >> the PRU-ICSS IP.
> > >
> > > Just get rid of the top level status = "disabled". The default
> > > is enabled, and the device is there for sure inside the SoC.
> > > And then there's no need for pointless status = "okay" tinkering
> > > in the board specific dts files so no need for this patch.
> >
> > The IP is not available on all SoCs, and there are about 40 different
> > board files atm across AM33xx and AM437x, and am not sure what SoCs they
> > are actually using.
>
> Oh that issue again.. Maybe take a look at patch "[PATCH 2/3] bus: ti-sysc:
> Detect display subsystem related devices" if you can add runtime
> detection for the accelerators there similar to what I hadded for omap3.
> acclerators.
Sorry I meant instead patch "[PATCH 6/7] bus: ti-sysc: Implement SoC
revision handling".
Regards,
Tony
next prev parent reply other threads:[~2020-02-26 22:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 20:46 [PATCH 00/12] ti-sysc support for PRUSS Suman Anna
2020-02-25 20:46 ` [PATCH 01/12] dt-bindings: bus: ti-sysc: Add support for PRUSS SYSC type Suman Anna
2020-02-26 8:42 ` Roger Quadros
2020-02-26 16:38 ` Suman Anna
2020-02-26 18:31 ` Tony Lindgren
2020-02-25 20:46 ` [PATCH 02/12] " Suman Anna
2020-02-25 20:46 ` [PATCH 03/12] ARM: dts: AM33xx-l4: Update PRUSS interconnect target-module node Suman Anna
2020-02-25 20:46 ` [PATCH 04/12] ARM: dts: AM4372: Add the PRU-ICSS " Suman Anna
2020-02-25 20:46 ` [PATCH 05/12] ARM: dts: dra7: Add PRU-ICSS interconnect target-module nodes Suman Anna
2020-02-25 20:46 ` [PATCH 06/12] ARM: dts: am335x-bone-common: Enable PRU-ICSS interconnect node Suman Anna
2020-02-26 18:29 ` Tony Lindgren
2020-02-26 20:34 ` Suman Anna
2020-02-26 22:37 ` Tony Lindgren
2020-02-26 22:39 ` Tony Lindgren [this message]
2020-02-27 0:58 ` Suman Anna
2020-02-27 2:07 ` Tony Lindgren
2020-02-27 21:28 ` Suman Anna
2020-02-27 21:30 ` Tony Lindgren
2020-02-25 20:46 ` [PATCH 07/12] ARM: dts: am335x-evm: " Suman Anna
2020-02-25 20:46 ` [PATCH 08/12] ARM: dts: am335x-evmsk: " Suman Anna
2020-02-25 20:46 ` [PATCH 09/12] ARM: dts: am335x-icev2: " Suman Anna
2020-02-25 20:46 ` [PATCH 10/12] ARM: dts: am437x-gp-evm: " Suman Anna
2020-02-25 20:46 ` [PATCH 11/12] ARM: dts: am437x-sk: " Suman Anna
2020-02-25 20:46 ` [PATCH 12/12] ARM: dts: am437x-idk: " Suman Anna
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=20200226223921.GB37466@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=s-anna@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.