From owner-freebsd-arm@FreeBSD.ORG Thu Feb 19 01:49:36 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3CB28DDA for ; Thu, 19 Feb 2015 01:49:36 +0000 (UTC) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E77633B7 for ; Thu, 19 Feb 2015 01:49:35 +0000 (UTC) Received: by wesu56 with SMTP id u56so4548342wes.10 for ; Wed, 18 Feb 2015 17:49:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Dqj7Y/IO0kr8S7Qhc8QuFUjZQ4vGSP8p9RJcky2QL5U=; b=x04pq5rCHrnRHBoI6yxsq38KD1cObTNHK+GmYY0lHOMKwugYYm61sVBj0MrJ7nZ6Tt vZnOh9aw7UenMoxhwTdrsbiC1W0F7ltBefLzl4pMrJsMKDK+dukPi3Ic6SRSf78q2T/R 0TEMxWAZZb+kEsI8DhJ3+hdf9mVfD4Pk7eBdbjAszsLvSw3jYbFKoxsI06zvb4bbxkGE g57HRKN9gWJIydFI0PGjuXLAZ6jjFRVBvatYRyemK+8U6p11Zmyc/yiGtbcjb6Fo1Gng VWjkRqwBK/Dnfy3acRBLtpmPXjjlRCWQ4kCOnqk47Csng3Jgpq5m6dOz5zAgSciPuFjI N/7Q== MIME-Version: 1.0 X-Received: by 10.180.92.226 with SMTP id cp2mr2112764wib.67.1424310573812; Wed, 18 Feb 2015 17:49:33 -0800 (PST) Received: by 10.217.170.196 with HTTP; Wed, 18 Feb 2015 17:49:33 -0800 (PST) In-Reply-To: <20150216093418.3d1be83b@zeta.dino.sk> References: <20150216093418.3d1be83b@zeta.dino.sk> Date: Wed, 18 Feb 2015 23:49:33 -0200 Message-ID: Subject: Re: Raspberry Pi SPI device example? From: Luiz Otavio O Souza To: Milan Obuch Content-Type: text/plain; charset=UTF-8 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 01:49:36 -0000 On 16 February 2015 at 06:34, Milan Obuch wrote: > Hi, > > I have little display attached to my raspberry, description found at > https://learn.adafruit.com/adafruit-pitft-28-inch-resistive-touchscreen-display-raspberry-pi > > It uses SPI interface for bouth display module and touch panel overlay, > so my question is - do we have any example how a SPI connected device > could be used? This module uses ILI9341 as TFT driver/controller and > STMPE610 for touch screen interface, both in SPI mode. As datasheets > are available on internet, it should not be too hard to write a driver, > but first some example would be great... > > Do we have anything like this? I could try to look how it is done on > raspbian linux, but as internally this is totally different, I would > like to avoid this, not to mention I have a hard time understand linux > kernel sources... > > Regards, > Milan Hi Milan, ATM we only support SPI devices as kernel drivers (no userland support yet). I guess you could add a vt(4) driver for ILI9341. The SPI drivers currently in tree are: - sys/arm/lpc/ssd1289.c - sys/arm/samsung/exynos/chrome_ec_spi.c - sys/dev/flash/mx25l.c - sys/dev/flash/at45d.c - sys/mips/atheros/pcf2123_rtc.c Luiz