From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound.icp-qv1-irony-out2.iinet.net.au (outbound.icp-qv1-irony-out2.iinet.net.au [203.59.1.107]) by ozlabs.org (Postfix) with ESMTP id 6F100DDE00 for ; Tue, 22 Jul 2008 16:42:57 +1000 (EST) Subject: Re: UIO not working on ppc405 onchip registers From: Ben Nizette To: Markus Brunner In-Reply-To: <20080722061730.GB12576@digi.com> References: <200807212152.16080.super.firetwister@gmail.com> <20080722061730.GB12576@digi.com> Content-Type: text/plain Date: Tue, 22 Jul 2008 16:42:47 +1000 Message-Id: <1216708967.4004.238.camel@moss.renham> Mime-Version: 1.0 Cc: "linuxppc-dev@ozlabs.org" , "linux-embedded@vger.kernel.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hey Markus, > > > > +config UIO_GPIO > > + tristate "Driver for PPC_4xx GPIO" As an aside, you sure you want to do this anyway? I'd suggest that you just do a gpio chip driver for this, tie it in to gpiolib and use the gpiolib user interface (which IIRC has only made it as far as -mm but is on the way up). This gives kernel internals nice access to the pins as well through the standard gpio framework. Thanks :-) --Ben.