From owner-freebsd-arm@freebsd.org Sat Apr 1 23:13:31 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1E6DD296D4 for ; Sat, 1 Apr 2017 23:13:31 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 99FEBE3 for ; Sat, 1 Apr 2017 23:13:31 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cuSCz-000DDq-4k; Sat, 01 Apr 2017 16:13:31 -0700 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v31NDOJu050829; Sat, 1 Apr 2017 16:13:24 -0700 (PDT) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Sat, 1 Apr 2017 16:13:24 -0700 From: Oleksandr Tymoshenko To: ash Cc: freebsd-arm@freebsd.org Subject: Re: BBB spi dts follow up Message-ID: <20170401231324.GA50794@bluezbox.com> References: <3b095b47-f3fb-488f-92f3-518e69d282c1@aeria.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b095b47-f3fb-488f-92f3-518e69d282c1@aeria.net> X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: ash (ash@aeria.net) wrote: > I decompiled the stock dts to get started with: > > #dtc -I dtb -O dts /boot/dtb/beaglebone-black.dtb ... skipped ... > But still no /dev/spi0 device. Any pointers are welcome. There is no /dev/spi0 in FreeBSD at the moment. The only way to access SPI from userland is by using spigen device. With later HEAD builds (post r314934) you can load it as a module: "kldload spigen" otherwise you'll need to add it to kernel config as a "device spigen". [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: github.com] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2017 23:13:31 -0000 ash (ash@aeria.net) wrote: > I decompiled the stock dts to get started with: > > #dtc -I dtb -O dts /boot/dtb/beaglebone-black.dtb ... skipped ... > But still no /dev/spi0 device. Any pointers are welcome. There is no /dev/spi0 in FreeBSD at the moment. The only way to access SPI from userland is by using spigen device. With later HEAD builds (post r314934) you can load it as a module: "kldload spigen" otherwise you'll need to add it to kernel config as a "device spigen". spigen functionality is very limited, you can't specify SPI mode or CS line. General procedure is to open /dev/spigen0 with O_RDWR and then use ioctls to transfer data. You can use this example as a simple reference: https://github.com/gonzoua/freebsd-embedded-demos/blob/master/libssd1306/ssd1306_spi.c#L86 -- gonzo