Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp623823imm; Thu, 31 May 2018 06:41:56 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLiS3WBFybsOZBB0gdDv9xWDf2mZP2VAMu75bHzthRGGh34qbjteXq+5aV6fN0gQtxcyI7a X-Received: by 2002:a62:a0c:: with SMTP id s12-v6mr6911441pfi.33.1527774116287; Thu, 31 May 2018 06:41:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527774116; cv=none; d=google.com; s=arc-20160816; b=K/+Hql8S6wQ7a+lPcVs57Ennc1Iy9yZUCUoBYbZUJhn8gqvsLsoNPVzGRntc5m86WK dbyL5U7++R/zPAS/tIr0Gjq5+GU8AzLTpidm0zHHQvQLwAABf2j2kLk/ueQ2W0DWmxod 9ckIrT4ZGcOzv6Q+dXBcWXD0tARftmtKKnDlOUPLyI/7LVVQxKufrzeN7n7a5jVAG6is kjvC7REZEchscBNMRLHiskGfTxCloxjFMBsAF1MFKzUC6QJPVuSoJE/2ae2uY60EkaUN 1113DZDlrENUPFR+13MIX1QZddIualGRjYxr8e8RfslzavEqsAUb0csmPIzj9wjCD2Gm xusw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=NVbKgfHh6iVKzo87pl4NdoKAjVrWH37m+2z6y4Tz+J4=; b=fh3Hf+VGfnqLVbGhTrOBKJISCVNIyUPgP8QqoyyLBbRsc/uwkeUcxnt0Wd/tHwwFPA 8RTgelS1Ss35hZAs/LTkdOipH0XO+M7M3hVlbjsHX2ADZAF0afK1zx1JMIk9l1tB7e6x kHeD9docfMIYnJRoZoZSGoG194/ZCiBfBdX1s38jp7RlWZwrsZdF9iPDRB4WRVwcQMwo uPfP8IwKw2n3undQZ3fJDnwyGxTRWEqwmOZ16yDUqzatqdN4z0IkR0LJwzMxMGfmnxPC zV2OZF7S5pDeRpIQZ8sY7YCiaiMzSav3LhCcbQfZJclcNJx0ubRuHmogaoexl6980StS OKnA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a7-v6si27842073pgu.26.2018.05.31.06.41.42; Thu, 31 May 2018 06:41:56 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755207AbeEaNlQ (ORCPT + 99 others); Thu, 31 May 2018 09:41:16 -0400 Received: from muru.com ([72.249.23.125]:45396 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755042AbeEaNlN (ORCPT ); Thu, 31 May 2018 09:41:13 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 594F6809F; Thu, 31 May 2018 13:43:35 +0000 (UTC) Date: Thu, 31 May 2018 06:41:09 -0700 From: Tony Lindgren To: Faiz Abbas Cc: Rob Herring , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, bcousson@baylibre.com, paul@pwsan.com, t-kristo@ti.com Subject: Re: [PATCH v2 5/6] ARM: dts: Add generic interconnect target module node for MCAN Message-ID: <20180531134109.GJ5705@atomide.com> References: <20180530141133.3711-1-faiz_abbas@ti.com> <20180530141133.3711-6-faiz_abbas@ti.com> <20180531040638.GA26751@rob-hp-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Faiz Abbas [180531 11:27]: > On Thursday 31 May 2018 09:36 AM, Rob Herring wrote: > > On Wed, May 30, 2018 at 07:41:32PM +0530, Faiz Abbas wrote: > >> --- a/arch/arm/boot/dts/dra76x.dtsi > >> +++ b/arch/arm/boot/dts/dra76x.dtsi > >> @@ -11,6 +11,25 @@ > >> / { > >> compatible = "ti,dra762", "ti,dra7"; > >> > >> + ocp { > >> + > >> + target-module@0x42c00000 { > > > > Build your dtb with W=1 and fix warnings you add (drop '0x'). > > Sure, Will fix this. > > > > This is a CAN bus controller? If so, then use 'can' for node name. > > Yes but I am using m_can along the lines of dcan in other boards (For > example, see arch/arm/boot/dts/am33xx.dtsi:1046). Are you saying all CAN > controllers should only be called can? The module should be target-module@42c00000 and the child(ren) can@1a00 or mcan@1a00 if mcan is different from can. Regards, Tony