From mboxrd@z Thu Jan 1 00:00:00 1970 From: vladoman@gmail.com (Vladimir Pantelic) Date: Thu, 06 Jun 2013 14:51:18 +0200 Subject: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) In-Reply-To: References: <51AFA6DD.3000202@wwwdotorg.org> <1370469574.18839.33.camel@localhost> <1370475609.20454.44.camel@localhost> <1370477958.20454.68.camel@localhost> Message-ID: <51B085C6.3000605@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org luke.leighton wrote: > On Thu, Jun 6, 2013 at 1:19 AM, Henrik Nordstr?m > wrote: >> tor 2013-06-06 klockan 00:54 +0100 skrev luke.leighton: >> >>> > 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? >> >> What I said before. > > idea: hook into devicetree gpio functions to allow script-fex gpio > functions to gain access in a separate module? that sort of thing. > >> Go with DT for the kernel. There is no need for two configuration >> mechanisms doing the same thing. Disguise it in fex form (and >> translator) if too hard for people with a DOS editior to configure. > > what methods for doing that. i need proposals. 4 days on the clock. 4 days? WTF? since when did setting an ultimatum to the kernel community work? From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Pantelic Subject: Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) Date: Thu, 06 Jun 2013 14:51:18 +0200 Message-ID: <51B085C6.3000605@gmail.com> References: <51AFA6DD.3000202@wwwdotorg.org> <1370469574.18839.33.camel@localhost> <1370475609.20454.44.camel@localhost> <1370477958.20454.68.camel@localhost> Reply-To: Linux on small ARM machines Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; Format="flowed" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: arm-netbook-bounces@lists.phcomp.co.uk Sender: "arm-netbook" To: Linux on small ARM machines Cc: devicetree-discuss , Linux Kernel Mailing List , debian-arm@lists.debian.org, "jonsmirl@gmail.com" , ARM Linux Mailing List , debian-kernel@lists.debian.org List-Id: devicetree@vger.kernel.org bHVrZS5sZWlnaHRvbiB3cm90ZToKPiBPbiBUaHUsIEp1biA2LCAyMDEzIGF0IDE6MTkgQU0sIEhl bnJpayBOb3Jkc3Ryw7ZtCj4gPGhlbnJpa0BoZW5yaWtub3Jkc3Ryb20ubmV0PiB3cm90ZToKPj4g dG9yIDIwMTMtMDYtMDYga2xvY2thbiAwMDo1NCArMDEwMCBza3JldiBsdWtlLmxlaWdodG9uOgo+ Pgo+Pj4gPiBOb3QgcmVhbGx5IHRoZSBjYXNlLiBBY3R1YWxseSB0aGUgb3Bwb3NpdGUuIERUIGhh dmUgdGhpcyBhcyB3ZWxsLCBhbmQKPj4+ID4gaW50ZWdyYXRlZCBpbiBkZXZpY2UgcHJvYmluZy4g QWxsd2lubmVyIG5lZWQgdG8gaGFjayBldmVyeSBkcml2ZXIgdXNlZAo+Pj4gPiB0byBhZGQgdGhl aXIgZ3BpbyByZXF1ZXN0cyB0byBoYXZlIHBpbm11eGluZyB0cmlnZ2VyZWQuCj4+Pgo+Pj4gIGF1 Z2guICBvay4gIHNvbHV0aW9ucy4gIHdoYXQgYXJlIHRoZSBzb2x1dGlvbnMgaGVyZT8KPj4KPj4g V2hhdCBJIHNhaWQgYmVmb3JlLgo+Cj4gICBpZGVhOiBob29rIGludG8gZGV2aWNldHJlZSBncGlv IGZ1bmN0aW9ucyB0byBhbGxvdyBzY3JpcHQtZmV4IGdwaW8KPiBmdW5jdGlvbnMgdG8gZ2FpbiBh Y2Nlc3MgaW4gYSBzZXBhcmF0ZSBtb2R1bGU/ICB0aGF0IHNvcnQgb2YgdGhpbmcuCj4KPj4gR28g d2l0aCBEVCBmb3IgdGhlIGtlcm5lbC4gVGhlcmUgaXMgbm8gbmVlZCBmb3IgdHdvIGNvbmZpZ3Vy YXRpb24KPj4gbWVjaGFuaXNtcyBkb2luZyB0aGUgc2FtZSB0aGluZy4gRGlzZ3Vpc2UgaXQgaW4g ZmV4IGZvcm0gKGFuZAo+PiB0cmFuc2xhdG9yKSBpZiB0b28gaGFyZCBmb3IgcGVvcGxlIHdpdGgg YSBET1MgZWRpdGlvciB0byBjb25maWd1cmUuCj4KPiAgIHdoYXQgbWV0aG9kcyBmb3IgZG9pbmcg dGhhdC4gIGkgbmVlZCBwcm9wb3NhbHMuICA0IGRheXMgb24gdGhlIGNsb2NrLgoKNCBkYXlzPyBX VEY/IHNpbmNlIHdoZW4gZGlkIHNldHRpbmcgYW4gdWx0aW1hdHVtIHRvIHRoZSBrZXJuZWwKY29t bXVuaXR5IHdvcms/CgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fCmFybS1uZXRib29rIG1haWxpbmcgbGlzdCBhcm0tbmV0Ym9va0BsaXN0cy5waGNvbXAu Y28udWsKaHR0cDovL2xpc3RzLnBoY29tcC5jby51ay9tYWlsbWFuL2xpc3RpbmZvL2FybS1uZXRi b29rClNlbmQgbGFyZ2UgYXR0YWNobWVudHMgdG8gYXJtLW5ldGJvb2tAZmlsZXMucGhjb21wLmNv LnVr From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933238Ab3FFMvY (ORCPT ); Thu, 6 Jun 2013 08:51:24 -0400 Received: from mail-ee0-f45.google.com ([74.125.83.45]:44613 "EHLO mail-ee0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932403Ab3FFMvW (ORCPT ); Thu, 6 Jun 2013 08:51:22 -0400 Message-ID: <51B085C6.3000605@gmail.com> Date: Thu, 06 Jun 2013 14:51:18 +0200 From: Vladimir Pantelic User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17 MIME-Version: 1.0 To: Linux on small ARM machines CC: devicetree-discuss , Linux Kernel Mailing List , debian-arm@lists.debian.org, "jonsmirl@gmail.com" , ARM Linux Mailing List , debian-kernel@lists.debian.org Subject: Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) References: <51AFA6DD.3000202@wwwdotorg.org> <1370469574.18839.33.camel@localhost> <1370475609.20454.44.camel@localhost> <1370477958.20454.68.camel@localhost> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org luke.leighton wrote: > On Thu, Jun 6, 2013 at 1:19 AM, Henrik Nordström > wrote: >> tor 2013-06-06 klockan 00:54 +0100 skrev luke.leighton: >> >>> > 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? >> >> What I said before. > > idea: hook into devicetree gpio functions to allow script-fex gpio > functions to gain access in a separate module? that sort of thing. > >> Go with DT for the kernel. There is no need for two configuration >> mechanisms doing the same thing. Disguise it in fex form (and >> translator) if too hard for people with a DOS editior to configure. > > what methods for doing that. i need proposals. 4 days on the clock. 4 days? WTF? since when did setting an ultimatum to the kernel community work?