Date: Sat, 3 Nov 2018 22:01:56 +0100 From: Bernd Walter <ticso@cicely7.cicely.de> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-arm@freebsd.org, Bernd Walter <ticso@cicely7.cicely.de>, ticso@cicely.de Subject: Re: How to add custom dts entries Message-ID: <20181103210156.GE79858@cicely7.cicely.de> In-Reply-To: <20181103205455.GD79858@cicely7.cicely.de> References: <20181103200709.GB79858@cicely7.cicely.de> <1541277990.52306.4.camel@freebsd.org> <20181103205455.GD79858@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 03, 2018 at 09:54:55PM +0100, Bernd Walter wrote: > On Sat, Nov 03, 2018 at 02:46:30PM -0600, Ian Lepore wrote: > > We do have overlay support now. I don't know much about using it, > > hopefully those who do will reply with details. > > That's good to know. > Hope for an answer too ;-) > > > There have also been updates to the SPI world. Your apa102led0 fdt node > > now requires a "spi-max-frequency" property, the value is the bus speed > > to use when communicating with that device, in Hz (different devices on > > the same bus can now have different speeds, and there is no concept of > > a default speed). Also, the chipsel number should be in a reg= > > property, but we still support spi-chipselect= too for backwards > > compatibility. > > Ah, important information. > I had been using dev.spi.0.clock to increase speed. > Obviously dev.spi doesn't even exists anymore. > Have to check about the CS, technically it is a dummy value anyway, > since the APA102 LEDs don't have a chip select and are the only > device connected to the SPI. I see, there is some overlay setup done for spigen(4). Didn't know we have userland spi support already. Nice addition. However, the DS18B20/ow_temp(4) still needs the onewire setup. -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181103210156.GE79858>