From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-187.mta1.migadu.com (out-187.mta1.migadu.com [95.215.58.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 110D0331EBC for ; Sat, 4 Jul 2026 09:54:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.187 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783158888; cv=none; b=XvIog7xbud7/tJUs41Tgtizv7wXrfgKxuQhDhGo0HA410tLSk20GqzxZgW1XRMSvsD/afEyGt0HsPceYWaopUpLTFpuJM6XDqTQ+L3lwDW+iRmI0qp6mlLTK5fEvOTcJOyWSZ9La5RGXFpMfYgVGhkNAxe5Eb/tWaRe8ik9mjN4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783158888; c=relaxed/simple; bh=d4FzgPzMAfTw3eD2clLSz3kLvxePfHTw3NTAXiGBYZ8=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=DJ32etlEVvSyW4epxh5VLS1E89DUKC+8IuzxP1pGLVE8ajHHM9P+IC2OGjHBQ9yuGjiOrohSzJdpIAz1jJMD8Gl8o46UJ4tt6LDpc2nwoxYraG1WiMkd0nzyiHCgJK5/eboM5clEpwVubqUdkjovxGyq+llmEZ0PeVKxj0B/a7A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow-tech.com; spf=pass smtp.mailfrom=cknow-tech.com; dkim=pass (2048-bit key) header.d=cknow-tech.com header.i=@cknow-tech.com header.b=Kas5S/+E; arc=none smtp.client-ip=95.215.58.187 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow-tech.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow-tech.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow-tech.com header.i=@cknow-tech.com header.b="Kas5S/+E" Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow-tech.com; s=key1; t=1783158883; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gwSOPRwPe16md58gxuRwvnrh/zOt3EcNn/2KFaD5eL4=; b=Kas5S/+E5faZ6tGsC3Od6zFmgPLB0QI5dwtnD9T+vrUTRkUxkwYhbQX09vex7b+YyLFpso DCLLST39THRf9qOm/obiooOuvpjt15Nh7bjLPsWaU5YIB/ZfS+5SyuYWGxvHGC7LgoGfG6 t+tpHKTDTc14LXDhr2HqkVKUW9v6YHYjhTMaGyGVDXIjuHqAXxg3K5SM7d4BcUFUXfVMA8 bA4+/yA/oEYLPdJRDOcIMeVAxOG4ZssKcQH4q0sxvvEQ4eXvUtb5l+YmnTR39o4cnFD7xz WQYmrM7B0zG345JVEKb4D1zPKr+JufARpjpcvprEfbweF2HqmF6gmR1eESoT/g== Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Sat, 04 Jul 2026 11:54:36 +0200 Message-Id: Cc: "Rob Herring" , "Krzysztof Kozlowski" , "Conor Dooley" , "Heiko Stuebner" , , , Subject: Re: [PATCH 00/12] arm64: dts: rockchip: Add NanoPi M6 board X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Diederik de Haas" To: "Joachim Eastwood" , "Diederik de Haas" References: <20260703-nanopi-m6-v1-0-8344a1559519@gmail.com> In-Reply-To: X-Migadu-Flow: FLOW_OUT Hi Joachim, On Fri Jul 3, 2026 at 10:23 PM CEST, Joachim Eastwood wrote: > On Fri, 3 Jul 2026 at 13:30, Diederik de Haas w= rote: >> On Fri Jul 3, 2026 at 12:07 AM CEST, Joachim Eastwood via B4 Relay wrote= : >> > This patch series add support for the NanoPi M6. This board is very >> > similar to the NanoPi R6C and R6S boards which are already supported. >> > >> > Main differences: >> > * M.2 M-key slot with PCIe (Also present on R6C) >> > * M.2 E-key slot with PCIe and USB (from hub) >> > * 1 additional USB 2.0 port from an on-board USB hub >> > * RT5616 audio CODEC >> >> This seems to be the M6 (2405 aka 'V1')? > Yes, correct. This patch set is for the original M6 board. V1 if you like= . > >> Because there is now also a M6V2 (2603), which uses an ES8389 CODEC: >> https://www.friendlyelec.com/index.php?route=3Dproduct/product&path=3D69= &product_id=3D319 > I did notice there was a new version, but I hadn't given it much thought. > >> Is it useful to already take the 2 M6 variants into account with this pa= tch set? > Yes, I think you are right. > > How about this setup: > rk3588s-nanopi-m6.dtsi > rk3588s-nanopi-m6v1.dts > rk3588s-nanopi-m6v2.dts > This mimics the setup for the R6 series boards with rk3588s-nanopi-r6.dts= i > and rk3588s-nanopi-r6[cs].dts. Seems fine. You could drop the 'v1' as I only used that to differentiate wi= th the V2. OTOH, I'm always 'struggling' how to identify the original NanoPC-T= 6. I do like consistency, so mimicing the setup for R6 is nice :-) > Note that I will not make the v2 board part of this patchset since I > am unable to test it. But as you said we can take it into account now. Agreed. My concern was about trying to prevent another complete reorganizat= ion once someone decides to upstream support for V2 (2603). >> https://wiki.friendlyelec.com/wiki/index.php/NanoPi_M6#Schematic.2C_PCB_= CAD_File >> https://wiki.friendlyelec.com/wiki/index.php/NanoPi_M6V2#Schematic.2C_PC= B_CAD_File > I did a quick comparison of the schematics and noticed the following > differences: > * New CODEC; ES8389 > * A new "User" button connected to a gpio line. > * Different USB 2.0 hub: CH334P (may not be relevant for DT) > * Different USB PD power solution (not relevant for DT) At the end of the M6V2 product page, there's also a comparison with 'V1': https://www.friendlyelec.com/image/catalog/description/M6V2_en_13.jpg It's under the heading 'Comparison', but it's part of the picture so you ca= n't search for it. Dunny why FriendlyElec does that, but they do it consistentl= y. Cheers, Diederik