From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joseph Lo Subject: Re: [PATCH V2 03/10] Documentation: dt-bindings: firmware: tegra: add bindings of the BPMP Date: Mon, 18 Jul 2016 14:42:43 +0800 Message-ID: <578C7A63.1000004@nvidia.com> References: <20160705090431.5852-1-josephl@nvidia.com> <20160705090431.5852-4-josephl@nvidia.com> <5786995A.1090706@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5786995A.1090706-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephen Warren , Thierry Reding , Alexandre Courbot Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Rob Herring , Mark Rutland , Peter De Schrijver , Matthew Longnecker , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Jassi Brar , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Catalin Marinas , Will Deacon List-Id: linux-tegra@vger.kernel.org On 07/14/2016 03:41 AM, Stephen Warren wrote: > On 07/05/2016 03:04 AM, Joseph Lo wrote: >> The BPMP is a specific processor in Tegra chip, which is designed for >> booting process handling and offloading the power management, clock >> management, and reset control tasks from the CPU. The binding document >> defines the resources that would be used by the BPMP firmware driver, >> which can create the interprocessor communication (IPC) between the CPU >> and BPMP. > >> diff --git >> a/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt >> b/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt > >> +- Documentation/devicetree/bindings/mailbox/mailbox.txt >> +- Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt > >> +- Documentation/devicetree/bindings/clock/clock-bindings.txt >> +- include/dt-bindings/clock/tegra186-clock.h >> +- Documentation/devicetree/bindings/reset/reset.txt >> +- include/dt-bindings/reset/tegra186-reset.h > > If you end up needing to repost this, it would be nice to make all those > file references more generic. In particular, some SW projects store > binding docs somewhere other than Documentation/devicetree/bindings/ > (e.g. U-Boot uses doc/device-tree-bindings/), and it's possible that the > header files aren't stored in include/ but somewhere else. To make these > file references valid everywhere, I'd suggest using relative paths for > the binding docs, and #include style paths for the headers, e.g.: > > ../clock/clock-bindings.txt > > > OK. Will fix this. Thanks, -Joseph -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: josephl@nvidia.com (Joseph Lo) Date: Mon, 18 Jul 2016 14:42:43 +0800 Subject: [PATCH V2 03/10] Documentation: dt-bindings: firmware: tegra: add bindings of the BPMP In-Reply-To: <5786995A.1090706@wwwdotorg.org> References: <20160705090431.5852-1-josephl@nvidia.com> <20160705090431.5852-4-josephl@nvidia.com> <5786995A.1090706@wwwdotorg.org> Message-ID: <578C7A63.1000004@nvidia.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 07/14/2016 03:41 AM, Stephen Warren wrote: > On 07/05/2016 03:04 AM, Joseph Lo wrote: >> The BPMP is a specific processor in Tegra chip, which is designed for >> booting process handling and offloading the power management, clock >> management, and reset control tasks from the CPU. The binding document >> defines the resources that would be used by the BPMP firmware driver, >> which can create the interprocessor communication (IPC) between the CPU >> and BPMP. > >> diff --git >> a/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt >> b/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt > >> +- Documentation/devicetree/bindings/mailbox/mailbox.txt >> +- Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt > >> +- Documentation/devicetree/bindings/clock/clock-bindings.txt >> +- include/dt-bindings/clock/tegra186-clock.h >> +- Documentation/devicetree/bindings/reset/reset.txt >> +- include/dt-bindings/reset/tegra186-reset.h > > If you end up needing to repost this, it would be nice to make all those > file references more generic. In particular, some SW projects store > binding docs somewhere other than Documentation/devicetree/bindings/ > (e.g. U-Boot uses doc/device-tree-bindings/), and it's possible that the > header files aren't stored in include/ but somewhere else. To make these > file references valid everywhere, I'd suggest using relative paths for > the binding docs, and #include style paths for the headers, e.g.: > > ../clock/clock-bindings.txt > > > OK. Will fix this. Thanks, -Joseph From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751445AbcGRGmu (ORCPT ); Mon, 18 Jul 2016 02:42:50 -0400 Received: from nat-hk.nvidia.com ([203.18.50.4]:6793 "EHLO hkmmgate101.nvidia.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750837AbcGRGms (ORCPT ); Mon, 18 Jul 2016 02:42:48 -0400 X-PGP-Universal: processed; by hkpgpgate101.nvidia.com on Sun, 17 Jul 2016 23:42:45 -0700 Subject: Re: [PATCH V2 03/10] Documentation: dt-bindings: firmware: tegra: add bindings of the BPMP To: Stephen Warren , Thierry Reding , Alexandre Courbot References: <20160705090431.5852-1-josephl@nvidia.com> <20160705090431.5852-4-josephl@nvidia.com> <5786995A.1090706@wwwdotorg.org> CC: , , Rob Herring , Mark Rutland , Peter De Schrijver , Matthew Longnecker , , Jassi Brar , , Catalin Marinas , Will Deacon From: Joseph Lo Message-ID: <578C7A63.1000004@nvidia.com> Date: Mon, 18 Jul 2016 14:42:43 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <5786995A.1090706@wwwdotorg.org> X-Originating-IP: [10.19.108.111] X-ClientProxiedBy: HKMAIL102.nvidia.com (10.18.16.11) To HKMAIL101.nvidia.com (10.18.16.10) Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/14/2016 03:41 AM, Stephen Warren wrote: > On 07/05/2016 03:04 AM, Joseph Lo wrote: >> The BPMP is a specific processor in Tegra chip, which is designed for >> booting process handling and offloading the power management, clock >> management, and reset control tasks from the CPU. The binding document >> defines the resources that would be used by the BPMP firmware driver, >> which can create the interprocessor communication (IPC) between the CPU >> and BPMP. > >> diff --git >> a/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt >> b/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt > >> +- Documentation/devicetree/bindings/mailbox/mailbox.txt >> +- Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt > >> +- Documentation/devicetree/bindings/clock/clock-bindings.txt >> +- include/dt-bindings/clock/tegra186-clock.h >> +- Documentation/devicetree/bindings/reset/reset.txt >> +- include/dt-bindings/reset/tegra186-reset.h > > If you end up needing to repost this, it would be nice to make all those > file references more generic. In particular, some SW projects store > binding docs somewhere other than Documentation/devicetree/bindings/ > (e.g. U-Boot uses doc/device-tree-bindings/), and it's possible that the > header files aren't stored in include/ but somewhere else. To make these > file references valid everywhere, I'd suggest using relative paths for > the binding docs, and #include style paths for the headers, e.g.: > > ../clock/clock-bindings.txt > > > OK. Will fix this. Thanks, -Joseph