From owner-freebsd-embedded@FreeBSD.ORG Sun Dec 4 12:14:35 2011 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEACB106564A for ; Sun, 4 Dec 2011 12:14:35 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 8AB2A8FC0C for ; Sun, 4 Dec 2011 12:14:35 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id D7BE71148C6 for ; Sun, 4 Dec 2011 13:14:34 +0100 (CET) From: Stefan Bethke Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 4 Dec 2011 13:14:34 +0100 Message-Id: To: freebsd-embedded@freebsd.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) Subject: ar71xx_gpio.c touches SPI_CS1 and 2? X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2011 12:14:35 -0000 I was looking into why I can't manipulate the USB led on my TL-WR1043ND, = and came across the SPI chip selects, which share GPIO 0 and 1, = respectively. The USB led is hooked up to GPIO 1. sys/mips/atheros/ar71xx_gpio.c:ar71xx_gpio_attach(device_t dev) enables = both chip selects, and detach disables them again. Two points: - how can we express different uses for those two pins on a per-board = config? - disabling the function is not correct for the gpio driver, I would = think. If you load and unload it as a module, I expect losing access to = the flash. Stefan --=20 Stefan Bethke Fon +49 151 14070811