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 S1752363AbcAMHfe (ORCPT <rfc822;w@1wt.eu>);
	Wed, 13 Jan 2016 02:35:34 -0500
Received: from mail-wm0-f66.google.com ([74.125.82.66]:35552 "EHLO
	mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750752AbcAMHfc convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 13 Jan 2016 02:35:32 -0500
From: Holger Schurig <holgerschurig@gmail.com>
To: Lothar =?utf-8?Q?Wa=C3=9Fmann?= <LW@KARO-electronics.de>
Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Kumar Gala <galak@codeaurora.org>, Mark Rutland <mark.rutland@arm.com>,
        Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
        Russell King <linux@arm.linux.org.uk>,
        Sascha Hauer <kernel@pengutronix.de>, Shawn Guo <shawnguo@kernel.org>,
        devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: imx6: add support for Ka-Ro electronics TX6S-8034 module
In-Reply-To: <1452621710-15336-2-git-send-email-LW@KARO-electronics.de>
	("Lothar \=\?utf-8\?Q\?Wa\=C3\=9Fmann\=22's\?\= message of "Tue, 12 Jan 2016
 19:01:48 +0100")
References: <1452621710-15336-1-git-send-email-LW@KARO-electronics.de>
	<1452621710-15336-2-git-send-email-LW@KARO-electronics.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
Date: Wed, 13 Jan 2016 08:35:28 +0100
Message-ID: <87h9iigce7.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Lothar Waßmann <LW@KARO-electronics.de> writes:

> +/ {
> +	model = "Ka-Ro electronics TX6S-8034 Module";
> +	compatible = "karo,imx6dl-tx6dl", "fsl,imx6dl";
> +	timestamp = __DATE__, __TIME__;

Is this needed or useful?

There's a movement that aims to do "reproducible builds" ...   being
able to recompile an image and verify it against the supplied can be
helpful for security audit purposes.


> +	display: display@di0 {
> +		compatible = "fsl,imx-parallel-display";
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&pinctrl_disp0_1>;
> +		interface-pix-fmt = "rgb24";
> +//		fsl,panel = <&lcd0_panel>;

Probably not for upstream inclusion?