From owner-freebsd-embedded@FreeBSD.ORG Fri Sep 6 22:20:25 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2915B536; Fri, 6 Sep 2013 22:20:25 +0000 (UTC) (envelope-from ray@freebsd.org) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id D90AC2DB3; Fri, 6 Sep 2013 22:20:24 +0000 (UTC) Received: from rnote.ddteam.net (52-58-135-95.pool.ukrtel.net [95.135.58.52]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 280A3C4935; Sat, 7 Sep 2013 01:20:23 +0300 (EEST) Date: Sat, 7 Sep 2013 01:20:04 +0300 From: Aleksandr Rybalko To: Ian Lepore Subject: Re: GPIO hint meanings Message-Id: <20130907012004.1a1d586d.ray@freebsd.org> In-Reply-To: <1378504840.1111.480.camel@revolution.hippie.lan> References: <1378488150.1637.5.camel@localhost> <097A9AFF-D291-4D9F-92CC-12E5E453F7C7@bsdimp.com> <1378504840.1111.480.camel@revolution.hippie.lan> Organization: FreeBSD.ORG X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) X-Operating-System: FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-embedded X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2013 22:20:25 -0000 On Fri, 06 Sep 2013 16:00:40 -0600 Ian Lepore wrote: > On Fri, 2013-09-06 at 13:42 -0600, Warner Losh wrote: > > On Sep 6, 2013, at 12:31 PM, Luiz Otavio O Souza wrote: > > > > > On 6 September 2013 14:22, Sean Bruno > > > wrote: > > > > > >> I think I have a fairly firm grasp on what some of the mips/gpio > > >> hints mean, e.g.: > > >> > > >> hint.gpio.0.pinmask > > >> hint.gpioled.0.at > > >> hint.gpioled.0.name > > >> hint.gpioled.0.pins > > >> > > >> Fairly straightforward. > > >> > > >> Now, what do these mean/do: > > >> > > >> hint.gpio.0.function_set > > >> hint.gpio.0.function_clear > > >> > > >> ? > > >> > > >> Sean > > >> > > >> p.s. I think I'll take this and thrash together a gpioled(4) and > > >> gpio(4) man page if I can understand better. > > >> > > > > > > > > > Hi Sean, > > > > > > Some of the GPIO pins on this SoC family (ar724x, ar71xx and > > > ar9xxx) can be set between GPIO and an alternate function. So > > > adding a pin to function_set enables this alternate function and > > > the function_clear disables it (sometimes the bootloader doesn't > > > initialize properly those pins). > > > > > > Each SoC has its own set of pins and functions. > > > > > > For ar71xx the pins 0 and 1 can be used as additional SPI chip > > > select outputs, pins 9 and 10 are used for UART and there are > > > also reserved pins for a SLIC/I2S interface. > > > > > > We really need a pinmux/pinctl type interface for this which is > > standard across drivers/platforms. > > > > The more ARM SoCs I look at, the less I think we could design a single > pinmux api that works for all of them. The number of things that can > be controlled varies from almost-nothing to chips that let you select > from one of a dozen different resistor strengths for pullup or > pulldown per pin. And that's not to mention really crazy things like > daisy-chaining pins so the signal also goes to another pin which can > be forced as an input even though it's normally a device output. +1 Looks like it is kind of Freescale i.MX club :))))) > > -- Ian > > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to > "freebsd-embedded-unsubscribe@freebsd.org" -- Aleksandr Rybalko