From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Daney Subject: Re: [PATCH 0/7] MIPS: Move device-tree files to a common location Date: Wed, 27 Aug 2014 12:33:35 -0700 Message-ID: <53FE328F.5040204@caviumnetworks.com> References: <1408651466-8334-1-git-send-email-abrestic@chromium.org> <20140823063113.GC23715@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andrew Bresticker Cc: Jonas Gorski , Geert Uytterhoeven , Olof Johansson , Florian Fainelli , Kumar Gala , Ralf Baechle , David Daney , Rob Herring , Linux-MIPS , Qais Yousef , Ian Campbell , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Pawel Moll , John Crispin , Mark Rutland , Jayachandran C , Paul Burton , James Hogan , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: devicetree@vger.kernel.org On 08/27/2014 11:30 AM, Andrew Bresticker wrote: > On Mon, Aug 25, 2014 at 8:17 AM, Jonas Gorski wrote: >> On Sat, Aug 23, 2014 at 9:50 PM, Geert Uytterhoeven >> wrote: >>> On Sat, Aug 23, 2014 at 8:31 AM, Olof Johansson wrote: >>>>>> arch/arm/boot/dts// >>>>>> >>>>>> Is this something we should do for the MIPS and update the other architectures >>>>>> to follow that scheme? >>>>> >>>>> I recall reading that as well and that it would be adopted for ARM64, >>>>> but that hasn't seemed to have happened. Perhaps Olof (CC'ed) will no >>>>> more. >>>> >>>> Yeah, I highly recommend having a directory per vendor. We didn't on ARM, >>>> and the amount of files in that directory is becoming pretty >>>> insane. Moving to a subdirectory structure later gets messy which is >>>> why we've been holding off on it. >>> >>> It would mean we can change our scripts to operate on "interesting" >>> DTS files from >>> >>> do-something-with $(git grep -l $vendor, -- arch/arm/boot/dts) >>> >>> to >>> >>> do-something-with arch/arm/boot/dts/$vendor/* >>> >>> which is easier to type... >> >> Btw, do you mean chip-vendor or device-vendor with vendor? >> Device-vendor could get a bit messy on the source part as the router >> manufacturers tend to switch them quite often. E.g. d-link used arm, >> mips and ubi32 chips from marvell, ubicom, broadcom, atheros, realtek >> and ralink for their dir-615 router, happily switching back and forth. >> There are 14 known different hardware revisions of it where the chip >> differed from the previous one. > > I'm going to assume it means chip/SoC vendor. That would result in > the following structure (I think): > > Octeon -> cavium/ To match the state of the art naming we have in other MIPS related directories, it should probably be "cavium-octeon/" (See arch/mips/cavium-octeon, and arch/mips/include/asm/mach-cavium-octeon) David Daney -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html