From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751657AbdJBOwz (ORCPT <rfc822;w@1wt.eu>);
        Mon, 2 Oct 2017 10:52:55 -0400
Received: from muru.com ([72.249.23.125]:42436 "EHLO muru.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751067AbdJBOwy (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 2 Oct 2017 10:52:54 -0400
Date: Mon, 2 Oct 2017 07:52:50 -0700
From: Tony Lindgren <tony@atomide.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: =?utf-8?Q?Beno=C3=AEt?= Cousson <bcousson@baylibre.com>,
        linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: am43xx-epos-evm: Enable SGX on EPOS boards
Message-ID: <20171002145250.GN4394@atomide.com>
References: <20170918173130.17657-1-afd@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170918173130.17657-1-afd@ti.com>
User-Agent: Mutt/1.9.0 (2017-09-02)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

* Andrew F. Davis <afd@ti.com> [170918 10:32]:
> From: Yogesh Siraswar <yogeshs@ti.com>
> 
> The SGX IP is valid and usable on AM438x devices, enable this
> here.

This still produces:

arch/arm/boot/dts/am43x-epos-evm.dts:796.1-5 Label or
path sgx not found

The parent node for the interconnect target module can be added
the same ways as done in "ARM: dts: Add nodes for missing omap4
interconnect target modules". But the child sgx device binding
still needs to be documented before we can add those.

Regards,

Tony