[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPweEDwS3tR=wh-bZJb3vqR8fVQra=3XxDitowGRdH9c7WRfmQ@mail.gmail.com>
Date: Thu, 6 Jun 2013 00:54:02 +0100
From: "luke.leighton" <luke.leighton@...il.com>
To: Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk>
Cc: 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,
"jonsmirl@...il.com" <jonsmirl@...il.com>,
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))
On Thu, Jun 6, 2013 at 12:40 AM, Henrik Nordström
<henrik@...riknordstrom.net> wrote:
> 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.
augh. ok. solutions. what are the solutions here?
l.
--
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