From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1BEEC35646 for ; Fri, 21 Feb 2020 16:14:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 988502073A for ; Fri, 21 Feb 2020 16:14:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=st.com header.i=@st.com header.b="qGaTrw5G" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729497AbgBUQOw (ORCPT ); Fri, 21 Feb 2020 11:14:52 -0500 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:30886 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729444AbgBUQOt (ORCPT ); Fri, 21 Feb 2020 11:14:49 -0500 Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 01LGCUZ2018389; Fri, 21 Feb 2020 17:14:26 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=from : to : cc : subject : date : message-id : mime-version : content-type; s=STMicroelectronics; bh=E9Mb7ngTP/ckY+QpFtc5xQAaCA17yjjNEfie0ZjjfD4=; b=qGaTrw5GZf1kCZgxRHU4BDd8dykC3GSYuEMYWIlBPcFeGZHZ2bIdMw0LPrSAPErA4sjz xRXEKNAFircbnm14WNVqPm2+6AI3f+mavYuY8cRgRe5UvPntdyZ6qLgNleeYOAtgmEDe WefAZgSmeaiZAlZoN9PBrlpXRMEGWciOKZ05252u8+nU3QG2rcdOVcc0EnwwbsTtsUg1 WlZw98IUIcSsIXWYcIxP+v0f00qr5VUBQXBEpF56IgmOs4COKJ//InRgrL1yeqhyWK0P fms1UdhM9r1zMDqbyb8xIyqfWBgaykhu2YEXDaead8Y4IPsT5I4y5nhbvmpzkBO8EthA 2A== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 2y8ub60bse-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 21 Feb 2020 17:14:26 +0100 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id B0F7210002A; Fri, 21 Feb 2020 17:14:20 +0100 (CET) Received: from Webmail-eu.st.com (sfhdag3node2.st.com [10.75.127.8]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id A0EE32BE258; Fri, 21 Feb 2020 17:14:20 +0100 (CET) Received: from localhost (10.75.127.49) by SFHDAG3NODE2.st.com (10.75.127.8) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Fri, 21 Feb 2020 17:14:19 +0100 From: Alexandre Torgue To: , Frank Rowand , Masahiro Yamada , Michal Marek , , CC: , Alexandre Torgue , , , , Ian Lepore Subject: [RFC PATCH v2 0/4] Add device tree build information Date: Fri, 21 Feb 2020 17:14:14 +0100 Message-ID: <20200221161418.20225-1-alexandre.torgue@st.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.75.127.49] X-ClientProxiedBy: SFHDAG8NODE1.st.com (10.75.127.22) To SFHDAG3NODE2.st.com (10.75.127.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138,18.0.572 definitions=2020-02-21_05:2020-02-21,2020-02-21 signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (with title it's better ;) Hi, The goal of this series is to add device tree build information in dtb. This information can be dtb build date, where devicetree files come from, who built the dtb ... Actually, same kind of information that you can find in the Linux banner which is printout during kernel boot. Having the same kind of information for device tree is useful for debugging and maintenance. A file (dtb-build.txt) containing a string with build information (e.g., >From Linux 5.5.0-rc1 by alex the Mon Jan 13 18:25:38 CET 2020) is generated by "gen_dtb_build_info.sh" script. This file has to be included manually in each dts file that would like to use this build information. of/fdt.c is modified to printout "build-info" property during Kernel boot and scripts/Makefile.lib is modified to call "gen_dtb_build_info.sh" script. Patch 1 & 2 script and of/fdt.c updates Patch 3 is an example of use in stm32mp157c-dk2.dts file. Patch 4 is a tentative to make it automatic (not yet 100% functional). regards Alex Changes since v1; - Remove modification in dtc (no more -B option) - Generate a file containing build info which is directly included in dts file. Regards Alex Alexandre Torgue (4): scripts: Add script to generate dtb build information of: fdt: print dtb build information ARM: dts: stm32: Add dtb build information entry for stm32mp157c-dk2 script: make automatic dtb build info generation arch/arm/boot/dts/stm32mp157c-dk2.dts | 1 + drivers/of/fdt.c | 9 +++++++++ scripts/Makefile.lib | 3 +++ scripts/gen_dtb_build_info.sh | 12 ++++++++++++ 4 files changed, 25 insertions(+) create mode 100755 scripts/gen_dtb_build_info.sh -- 2.17.1 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx08-00178001.pphosted.com ([91.207.212.93]:30886 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729444AbgBUQOt (ORCPT ); Fri, 21 Feb 2020 11:14:49 -0500 From: Alexandre Torgue Subject: [RFC PATCH v2 0/4] Add device tree build information Date: Fri, 21 Feb 2020 17:14:14 +0100 Message-ID: <20200221161418.20225-1-alexandre.torgue@st.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: robh+dt@kernel.org, Frank Rowand , Masahiro Yamada , Michal Marek , david@gibson.dropbear.id.au, sjg@chromium.org Cc: devicetree@vger.kernel.org, Alexandre Torgue , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, devicetree-compiler@vger.kernel.org, Ian Lepore (with title it's better ;) Hi, The goal of this series is to add device tree build information in dtb. This information can be dtb build date, where devicetree files come from, who built the dtb ... Actually, same kind of information that you can find in the Linux banner which is printout during kernel boot. Having the same kind of information for device tree is useful for debugging and maintenance. A file (dtb-build.txt) containing a string with build information (e.g., >From Linux 5.5.0-rc1 by alex the Mon Jan 13 18:25:38 CET 2020) is generated by "gen_dtb_build_info.sh" script. This file has to be included manually in each dts file that would like to use this build information. of/fdt.c is modified to printout "build-info" property during Kernel boot and scripts/Makefile.lib is modified to call "gen_dtb_build_info.sh" script. Patch 1 & 2 script and of/fdt.c updates Patch 3 is an example of use in stm32mp157c-dk2.dts file. Patch 4 is a tentative to make it automatic (not yet 100% functional). regards Alex Changes since v1; - Remove modification in dtc (no more -B option) - Generate a file containing build info which is directly included in dts file. Regards Alex Alexandre Torgue (4): scripts: Add script to generate dtb build information of: fdt: print dtb build information ARM: dts: stm32: Add dtb build information entry for stm32mp157c-dk2 script: make automatic dtb build info generation arch/arm/boot/dts/stm32mp157c-dk2.dts | 1 + drivers/of/fdt.c | 9 +++++++++ scripts/Makefile.lib | 3 +++ scripts/gen_dtb_build_info.sh | 12 ++++++++++++ 4 files changed, 25 insertions(+) create mode 100755 scripts/gen_dtb_build_info.sh -- 2.17.1