From owner-freebsd-arm@FreeBSD.ORG  Sat Feb 28 13:24:29 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 81B1F5E8
 for <freebsd-arm@freebsd.org>; Sat, 28 Feb 2015 13:24:29 +0000 (UTC)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id F122961C
 for <freebsd-arm@freebsd.org>; Sat, 28 Feb 2015 13:24:28 +0000 (UTC)
Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan)
 by mailhost.netlabit.sk with ESMTPA; Sat, 28 Feb 2015 14:24:25 +0100
 id 00DCA818.54F1C189.00008A36
Date: Sat, 28 Feb 2015 14:24:24 +0100
From: Milan Obuch <freebsd-arm@dino.sk>
To: Erich Dollansky <erichsfreebsdlist@alogt.com>
Subject: Re: Raspberry Pi with PiTFT - some GPIO weirdness
Message-ID: <20150228142424.6fed0ecf@zeta.dino.sk>
In-Reply-To: <20150228193658.6c872779@B85M-HD3-0.alogt.com>
References: <20150228111852.15affe31@zeta.dino.sk>
 <20150228193658.6c872779@B85M-HD3-0.alogt.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; i386-portbld-freebsd10.1)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-arm@freebsd.org
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2015 13:24:29 -0000

On Sat, 28 Feb 2015 19:36:58 +0800
Erich Dollansky <erichsfreebsdlist@alogt.com> wrote:

> Hi,
> 
> On Sat, 28 Feb 2015 11:18:52 +0100
> Milan Obuch <freebsd-arm@dino.sk> wrote:
> 
> > today I found some time to play a bit with my little display
> > attached to Rasoberry Pi, and I decided to test buttons connected
> > to GPIO, as this should work on FreeBSD already. According docs,
> > buttons are connected to GPIO lines 23, 22, 21 and 18, leftmost
> > first.
> > 
> > Using basic 'gpioctl -f /dev/gpioc0 -lv' command I found only first
> > one, on line 23, reacts. It has value 1 normally and 0 when pressed.
> > 
> you must setup the pins as inputs first before using them as inputs. I
> would not rely on any defaults.
> 
> Erich

According available docs, all GPIO are set to input mode after reset.
This seems not to be the case, but that's not my point. What was a bit
of surprise for me was even 'gpioctl -f /dev/gpioc0 -l' tells those
pins are in input mode ('pin nn<IN>'), it did not work. And fact that
even after power disconnect the state remains the same is even more
weird.

Anyway, I accept the necessity for setup, the question is, where should
these setup instruction go.

Regards,
Milan