Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 2 Jan 2020 11:33:59 -0800
From:   Tony Lindgren <tony@atomide.com>
To:     =?utf-8?B?QW5kcsOp?= Hentschel <nerv@dawncrow.de>
Cc:     linux@arm.linux.org.uk, robh+dt@kernel.org, mark.rutland@arm.com,
        bcousson@baylibre.com, linux-omap@vger.kernel.org,
        devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: dts: Move interconnect target module for
 omap3 sgx to separate dtsi files
Message-ID: <20200102193359.GE16702@atomide.com>
References: <20191230202037.28836-1-nerv@dawncrow.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20191230202037.28836-1-nerv@dawncrow.de>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

* André Hentschel <nerv@dawncrow.de> [191230 20:22]:
> Only dm3730 and am3715 come with SGX support

AFAIK dm3730 is just a marketing name for a catalog version of
omap3630. So using omap36xx.dtsi is correct and we should not
change that.

Can you please just add a minimal dm3725.dtsi that your board dts
can include and avoid disabling sgx in the board specific file?
That is assuming you have dm3725 with dsp and isp but no sgx.

You can read the detected SoC with:

# cat /sys/bus/soc/devices/soc0/machine

This avoids somebody (probably me again) patching all over the
board specific files trying to guess which SoC the device might
have.

Regards,

Tony