linux-kernel - Tegra device name for device tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 5 Jul 2011 11:22:30 -0700
From:	Stephen Warren <swarren@...dia.com>
To:	"Grant Likely (grant.likely@...retlab.ca)" 
	<grant.likely@...retlab.ca>
CC:	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Tegra device name for device tree

Grant et. al.,

It recently dawned on me that all the Tegra DeviceTree support is using a
marketing name for the SoC ("tegra250"). NVIDIA would prefer that we use
engineering names for the SoC (e.g. "tegra20" now, "tegra30" for an
upcoming SoC). The primary motivation for this is that engineering names
tend to be more stable and map more directly to the HW design.

Is it still possible to make this change, if I submit the appropriate
patches to do this? 

So, far, I see devicetree/next only refers to the Tegra serial port,
whereas devicetree/arm and devicetree/test refer to more Tegra devices in
this way. I'm not quite sure how the flow of patches works between these 3
trees. For the serial port, I obviously need to submit a patch against
devicetree/next, but I'm not so sure about which of devicetree/arm or
devicetree/test to target for the other devices.

Sorry for bringing this up so late in the game.

Thanks!

-- 
nvpublic

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/