On Sat 2015-12-26 00:40:12, Pali Rohár wrote:
> This patch adds adp1653 device into n900 DT structure. DT support in
> adp1653 driver is there since v4.2-rc1 version.
>
> Signed-off-by: Pali Rohár
Acked-by: Pavel Machek
--
(english)
On Sat 2015-12-26 00:32:25, Pali Rohár wrote:
> Driver for omap3 with documentation is there since v4.4-rc1.
>
> Signed-off-by: Pali Rohár
Acked-by: Pavel Machek
Tested-by: Pavel Machek
Thanks!
On Sat 2015-12-26 00:37:16, Pali Rohár wrote:
> Property names do not match real names needed by driver itself.
> This patch fix this problem.
>
> Signed-off-by: Pali Rohár
Acked-by: Pavel Machek
Now... if someone could convert adp1653 to the LED subsystem
Adds a new property "spi-word-wait-ns" to the spi-bus binding that allows
SPI slave devices to set a wait time between the transmission of words.
Signed-off-by: Marcus Weseloh
Reviewed-by: Maxime Ripard
Acked-by: Rob Herring
Marsboard A10 have four red LEDs, the first one can be used for heartbeat
indication.
Signed-off-by: Aleksei Mamlin
---
arch/arm/boot/dts/sun4i-a10-marsboard.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/sun4i-a10-marsboard.dts
Hi all,
This is the sixth version of the patch set that adds a new property
"spi-word-wait-ns" to the spi-bus binding to allow SPI slave devices to set
a wait time between the transmission of words. It modifies the spi_device
struct and slave device probing to read and store the new property.
This patch fixes multiple problems with the current clock calculations:
1. The A10/A20 datasheet contains the formula AHB_CLK / (2^(n+1)) to
calculate SPI_CLK from CDR1, but this formula is wrong. The actual
formula - determined by analyzing the actual waveforms - is
AHB_CLK / (2^n).
2. The
Modifies the sun4i SPI master driver to make use of the
"spi-word-wait-ns" property. This specific SPI controller needs 3 clock
cycles to set up the delay, which makes the minimum non-zero wait time
on this hardware 4 clock cycles.
Signed-off-by: Marcus Weseloh
---
Den 22.12.2015 20:01, skrev Eric Anholt:
After finally booting the RPi2 I get several messages of:
unexpected IRQ trap at vector 00
while typing _one_ character over uart.
We were doing some debugging of that recently. It seems that every once
in a while we get woken up but nothing shows
Eric Anholt writes:
> This should be a complete port of bcm2835 functionality to bcm2836
> (Raspberry Pi 2).
>
> Signed-off-by: Eric Anholt
> ---
>
> v2: Implement Arnd's feedback to not split to ARCH_BCM2836, and
> instead use more conditionals in
Allow the current for both RED and IR LEDs to be set via an device tree
property setting.
This is an optional setting that is useful for applications that have a
known glass attenuation factor.
Signed-off-by: Matt Ranostay
---
Add operating-points-v2, clock, and regulator supply properties
required by mt8173-cpufreq driver to enable it.
Signed-off-by: Pi-Cheng Chen
---
This patch is based on the patch[1] that adds underlying clock MUX for
MT8173 which is needed by mt8173-cpufreq driver but
Modify mt8173-cpufreq driver to get OPP-sharing information and set up
OPP table provided by operating-points-v2 bindings.
Signed-off-by: Pi-Cheng Chen
---
drivers/cpufreq/mt8173-cpufreq.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff
Don't skip cpu_dev->id when setting up cpumask for CPUs that share the
same OPP table. This might be helpful when handling cpumask without the
original CPU bitfield set.
Signed-off-by: Pi-Cheng Chen
---
drivers/base/power/opp/cpu.c | 4
1 file changed, 4
This series tries to migrate mt8173-cpufreq driver to use
operating-points-v2 bindings and add support for mt8173-cpufreq driver
v1->v2:
- update dev_pm_opp_of_get_sharing_cpus() to setup bitfield of original CPU
- rename OPP nodes in dts according to OPPv2 bindings in linux-next
Pi-Cheng Chen
15 matches
Mail list logo