Audio codec device tree entries
Timur Tabi
timur at freescale.com
Thu Oct 25 05:41:25 EST 2007
Jon Smirl wrote:
> Why are you using a vendor named directory? I don't believe vendor
> named directories are used anywhere in the kernel. The directories are
> always named after the platform or architecture. Vendor directories
> end up in a big mess if Freescale decides to sell a CPU to someone
> else.
Two reasons:
1) The sound/soc directory already has names like "at91" and "pxa", so I thought
"fsl" is appropriate.
2) There may not be any directories named "fsl", but there are plenty of files
with that name:
./arch/powerpc/boot/fsl-soc.c
./arch/powerpc/boot/fsl-soc.h
./arch/powerpc/boot/fsl-soc.o
./arch/powerpc/mm/fsl_booke_mmu.c
./arch/powerpc/platforms/fsl_uli1575.c
./arch/powerpc/sysdev/fsl_pci.c
./arch/powerpc/sysdev/fsl_pci.h
./arch/powerpc/sysdev/fsl_soc.c
./arch/powerpc/sysdev/fsl_soc.h
./arch/powerpc/sysdev/fsl_soc.o
./arch/ppc/mm/fsl_booke_mmu.c
./drivers/usb/gadget/fsl_usb2_udc.c
./drivers/usb/gadget/fsl_usb2_udc.h
./include/linux/fsl_devices.h
./include/config/fsl
Having said all that, if you really think sound/soc/powerpc is better than
sound/soc/fsl, I won't complain.
More information about the Linuxppc-dev
mailing list