Date: Wed, 29 Apr 2015 12:42:41 -0600 From: Ian Lepore <ian@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Tom Jones <jones@sdf.org>, "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: SPI User Space Interface Message-ID: <1430332961.1157.88.camel@freebsd.org> In-Reply-To: <CAJ-VmokuB6vXV-uP7ezXqdifcDmCDzN3Txg9HWpsDHKqhE3wqQ@mail.gmail.com> References: <20150426203344.GA27490@gmail.com> <CAJ-VmokuB6vXV-uP7ezXqdifcDmCDzN3Txg9HWpsDHKqhE3wqQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2015-04-26 at 20:06 -0700, Adrian Chadd wrote: > Hey, this is cool! > > What can we do to spibus to make it better? > It's been a while since I've worked with SPI on freebsd, but I remember that it needs support for bus speed and SPI mode (clock polarity and phase) on a per-chipsel basis. They need to be in the request struct sent down to the controller driver, because it's the device(-on-the-bus) driver that knows the max speed for the device and the mode it expects (although in my experience everything seems to use mode 3). -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1430332961.1157.88.camel>