On 06/02/2014 02:18 PM, Marcel Ziswiler wrote:
> On 06/02/2014 06:26 PM, Stephen Warren wrote:
>>> +pwmleds {
>>> +compatible = "pwm-leds";
>>> +
>>> +pwm3 {
>>> +label = "PWM3";
>>> +pwms = <&pwm 1 19600>;
>>> +max-brightness = <255>;
>>> +
On 06/02/2014 06:33 PM, Stephen Warren wrote:
I vaguely recall people speaking out against including "spidev" devices
in DT because they don't represent actual HW, but rather a way to
request that the SPI bus be exposed to user-space, which is a pure SW
issue. Wouldn't it be better if the spidev
On 06/02/2014 06:26 PM, Stephen Warren wrote:
+ toradex,colibri_t30
+ toradex,colibri_t30-eval-v3
Those don't seem to be related to Apalis support.
Yes, that's why I mentioned it in the commit message as follows:
>> While at it also add the device tree binding documentation for Apalis
>> T
On 06/01/2014 05:37 PM, Marcel Ziswiler wrote:
> This patch adds the device tree to support Toradex Apalis T30, a
> computer on module which can be used on different carrier boards.
>
> The module consists of a Tegra 3 SoC, two PMICs, 1 or 2 GB of DDR3L
> RAM, eMMC, an LM95245 temperature sensor c
On 06/01/2014 05:37 PM, Marcel Ziswiler wrote:
> This patch adds the device tree to support Toradex Apalis T30, a
> computer on module which can be used on different carrier boards.
>
> The module consists of a Tegra 3 SoC, two PMICs, 1 or 2 GB of DDR3L
> RAM, eMMC, an LM95245 temperature sensor c
This patch adds the device tree to support Toradex Apalis T30, a
computer on module which can be used on different carrier boards.
The module consists of a Tegra 3 SoC, two PMICs, 1 or 2 GB of DDR3L
RAM, eMMC, an LM95245 temperature sensor chip, an i210 resp. i211
gigabit Ethernet controller, an S
