From mboxrd@z Thu Jan 1 00:00:00 1970 From: maxime.ripard@free-electrons.com (Maxime Ripard) Date: Mon, 14 Nov 2016 09:55:40 +0100 Subject: [PATCH 2/3] ARM: dts: sunxi: add Allwinner H2+ dtsi In-Reply-To: <20161111164654.15273-2-icenowy@aosc.xyz> References: <20161111164654.15273-1-icenowy@aosc.xyz> <20161111164654.15273-2-icenowy@aosc.xyz> Message-ID: <20161114085540.x2hp5k7eyjv6l2dd@lukather> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sat, Nov 12, 2016 at 12:46:53AM +0800, Icenowy Zheng wrote: > Allwinner H2+ is a SoC so similar with H3 that H3 drivers and memory map > is known to work well on H2+, with both BSP kernel/firmware or the > mainline ones. > > So add a dtsi file which only include the H3 dtsi only, so we can add > H2+-specified nodes in the dtsi file when we find any software > difference between H2+ and H3. > > Signed-off-by: Icenowy Zheng I don't think we need that patch at all. You can do it just like we did for the R8 and R16, just include the H3 DTSI in your board. We'll create it if we need it at some point. Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Subject: Re: [PATCH 2/3] ARM: dts: sunxi: add Allwinner H2+ dtsi Date: Mon, 14 Nov 2016 09:55:40 +0100 Message-ID: <20161114085540.x2hp5k7eyjv6l2dd@lukather> References: <20161111164654.15273-1-icenowy@aosc.xyz> <20161111164654.15273-2-icenowy@aosc.xyz> Reply-To: maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4oz4gyehva5v7nxa" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20161111164654.15273-2-icenowy-ymACFijhrKM@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Icenowy Zheng Cc: Jonathan Corbet , Chen-Yu Tsai , Rob Herring , Mark Rutland , Russell King , linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-Id: devicetree@vger.kernel.org --4oz4gyehva5v7nxa Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline On Sat, Nov 12, 2016 at 12:46:53AM +0800, Icenowy Zheng wrote: > Allwinner H2+ is a SoC so similar with H3 that H3 drivers and memory map > is known to work well on H2+, with both BSP kernel/firmware or the > mainline ones. > > So add a dtsi file which only include the H3 dtsi only, so we can add > H2+-specified nodes in the dtsi file when we find any software > difference between H2+ and H3. > > Signed-off-by: Icenowy Zheng I don't think we need that patch at all. You can do it just like we did for the R8 and R16, just include the H3 DTSI in your board. We'll create it if we need it at some point. Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com --4oz4gyehva5v7nxa-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752905AbcKNIzs (ORCPT ); Mon, 14 Nov 2016 03:55:48 -0500 Received: from mail.free-electrons.com ([62.4.15.54]:35052 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752648AbcKNIzm (ORCPT ); Mon, 14 Nov 2016 03:55:42 -0500 Date: Mon, 14 Nov 2016 09:55:40 +0100 From: Maxime Ripard To: Icenowy Zheng Cc: Jonathan Corbet , Chen-Yu Tsai , Rob Herring , Mark Rutland , Russell King , linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-sunxi@googlegroups.com Subject: Re: [PATCH 2/3] ARM: dts: sunxi: add Allwinner H2+ dtsi Message-ID: <20161114085540.x2hp5k7eyjv6l2dd@lukather> References: <20161111164654.15273-1-icenowy@aosc.xyz> <20161111164654.15273-2-icenowy@aosc.xyz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4oz4gyehva5v7nxa" Content-Disposition: inline In-Reply-To: <20161111164654.15273-2-icenowy@aosc.xyz> User-Agent: Mutt/1.6.2-neo (2016-08-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --4oz4gyehva5v7nxa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 12, 2016 at 12:46:53AM +0800, Icenowy Zheng wrote: > Allwinner H2+ is a SoC so similar with H3 that H3 drivers and memory map > is known to work well on H2+, with both BSP kernel/firmware or the > mainline ones. >=20 > So add a dtsi file which only include the H3 dtsi only, so we can add > H2+-specified nodes in the dtsi file when we find any software > difference between H2+ and H3. >=20 > Signed-off-by: Icenowy Zheng I don't think we need that patch at all. You can do it just like we did for the R8 and R16, just include the H3 DTSI in your board. We'll create it if we need it at some point. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com --4oz4gyehva5v7nxa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYKXwMAAoJEBx+YmzsjxAgM4EP/0SPUIH9HT2dG/Giw0dvJ1uZ 1vA8rPdCYDg5LhmFjJV87yYAw1i6cTQUCv1N/mj7CMKXmRAtUp+mq4yOXAY7FmLw CUjEVPGSTn7Uh/xhTUTdXGmX8/s2XKEG2qn/0bn/IY6/yKvpn9syZX36u4SsPzgE ZlEdKz7y3YEys9ZudLtfXVJ/7JPOjmavIZk3cjBUf9y7bgCfm4oSm76lFl2TyVUY HjUiZEczJ+t3xiqSq4zwRjE4PrAiBBUrboJHWwA/j6WMnkdrVtKpW881O4vICl6J 8pCqUtWI5GT78ulUGCHStn+w7Ut7pKOcshHUdJDib2VzymzRw7K5PaIRL09JTQ8f /ZxFaQL4wBjdmjKwrWNNSssi63ieKqMB24EoMQPftpUm9VphDrshPbva7oB0G562 OI58AjjRrPzt6KxTNvCObRe53EWtoknxHrTNd4d6a0a4jXePPRuBR3hnMijiij6J IChLvKFOGZv7cckmM8B3BQ2PRGibsOpmom/ZoRnZQifGi9ejBedlcEbN7Fc50zCG 1Ryw1Ixf+L3cGV8WBxc7qV3HWpEsSG6eUivf9J6U8ozPesaebCt/UwBKl3Je4mce pYTj2W8S2WaHB1lRwQ73PSo8YkGCZJXSB7ODv01kgkG03G0MNOkuzY7ijC1CJYb+ 7VY7fRDeGS1rHmHVijvU =QqSK -----END PGP SIGNATURE----- --4oz4gyehva5v7nxa--