linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s-anna@ti.com (Suman Anna)
To: linux-arm-kernel@lists.infradead.org
Subject: [REPOST PATCH 1/4] ARM: dts: DRA7: Add dsp1_system syscon node
Date: Mon, 12 Oct 2015 17:32:59 -0500	[thread overview]
Message-ID: <561C351B.3060307@ti.com> (raw)
In-Reply-To: <20151012214304.GD23801@atomide.com>

Hi Tony,

On 10/12/2015 04:43 PM, Tony Lindgren wrote:
> * Suman Anna <s-anna@ti.com> [151002 16:27]:
>> The DSP_SYSTEM sub-module is a dedicated system control logic
>> module present within a DRA7 DSP processor sub-system. This
>> module is responsible for power management, clock generation
>> and connection to the device PRCM module.
>>
>> Add a syscon node for this module for the DSP1 processor
>> sub-system. This is added as a syscon node as it is a common
>> configuration module that can be used by the different IOMMU
>> instances and the corresponding remoteproc device.
>>
>> The node is added to the common dra7.dtsi file, as the DSP1
>> processor sub-system is mostly common across all the variants
>> of the DRA7 SoC family.
>>
>> Signed-off-by: Suman Anna <s-anna@ti.com>
>> ---
>>  arch/arm/boot/dts/dra7.dtsi | 5 +++++
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
>> index e289c706d27d..62055094e8d5 100644
>> --- a/arch/arm/boot/dts/dra7.dtsi
>> +++ b/arch/arm/boot/dts/dra7.dtsi
>> @@ -292,6 +292,11 @@
>>  				#thermal-sensor-cells = <1>;
>>  		};
>>  
>> +		dsp1_system: dsp_system at 40d00000 {
>> +			compatible = "syscon";
>> +			reg = <0x40d00000 0x100>;
>> +		};
>> +
>>  		sdma: dma-controller at 4a056000 {
>>  			compatible = "ti,omap4430-sdma";
>>  			reg = <0x4a056000 0x1000>;
> 
> Hmm so why would you want to set up a complete device as a syscon
> mapping rather than just doing ioremap on it?
> 
> What drivers will be sharing access to these registers?

Two different instances of the MMU for now, both get probed
independently. But there are other registers which a remoteproc driver
will mostly be interested in (like DSP_SYS_STAT for knowing the C66x
idle/active status).

regards
Suman

  reply	other threads:[~2015-10-12 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 23:23 [REPOST PATCH 0/4] Add DRA7 IOMMU DT nodes Suman Anna
2015-10-02 23:23 ` [REPOST PATCH 1/4] ARM: dts: DRA7: Add dsp1_system syscon node Suman Anna
2015-10-12 21:43   ` Tony Lindgren
2015-10-12 22:32     ` Suman Anna [this message]
2015-10-12 22:50       ` Tony Lindgren
2015-10-12 22:55         ` Tony Lindgren
2015-10-02 23:23 ` [REPOST PATCH 2/4] ARM: dts: DRA74x: Add dsp2_system " Suman Anna
2015-10-02 23:23 ` [REPOST PATCH 3/4] ARM: dts: DRA7: Add common IOMMU nodes Suman Anna
2015-10-02 23:23 ` [REPOST PATCH 4/4] ARM: dts: DRA74x: Add IOMMU nodes for DSP2 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=561C351B.3060307@ti.com \
    --to=s-anna@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).