[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1370475609.20454.44.camel@localhost>
Date: Thu, 06 Jun 2013 01:40:09 +0200
From: Henrik Nordström <henrik@...riknordstrom.net>
To: Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk>
Cc: "jonsmirl@...il.com" <jonsmirl@...il.com>,
devicetree-discuss <devicetree-discuss@...abs.org>,
Stephen Warren <swarren@...dotorg.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
debian-arm@...ts.debian.org,
ARM Linux Mailing List <linux-arm-kernel@...ts.infradead.org>,
debian-kernel@...ts.debian.org
Subject: Re: [Arm-netbook] getting allwinner SoC support upstream (was Re:
Uploading linux (3.9.4-1))
tor 2013-06-06 klockan 00:26 +0100 skrev luke.leighton:
> no john - they've only added it to the multiplexed sections of the
> drivers which they themselves have written. such as
> drivers/usb/sun{N}i_usb/*.[ch], drivers/block/nand/sun{N}_i,
> arch/arm/mach-sun{N}i and so on.
And a number of SPI device drivers, USB device drivers, vendor provided
device drivers, ......
> the script.fex system deals with the pinmux issue in a very neat way that:
>
> a) has very little impact on the rest of the kernel tree [citation
> needed! i'm saying that: could someone please confirm if it's true]
Not really the case. Actually the opposite. DT have this as well, and
integrated in device probing. Allwinner need to hack every driver used
to add their gpio requests to have pinmuxing triggered.
It is just layered a bit differently when using DT.
Regards
Henrik
--
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/
Powered by blists - more mailing lists