This is a driver for the Holtek HT16K33 LED controller with keyscan.
Signed-off-by: Robin van der Gracht
---
.../devicetree/bindings/display/ht16k33.txt| 42 ++
drivers/auxdisplay/Kconfig | 9 +
drivers/auxdisplay/Makefile| 1
This is a driver for the Holtek HT16K33 LED controller with keyscan.
Signed-off-by: Robin van der Gracht <ro...@protonic.nl>
---
.../devicetree/bindings/display/ht16k33.txt| 42 ++
drivers/auxdisplay/Kconfig | 9 +
drivers/auxdisplay/Ma
This is a driver for the Holtek HT16K33 LED controller with keyscan.
Signed-off-by: Robin van der Gracht <ro...@protonic.nl>
---
Changes in v2:
- Fixed build error reported by kbuild test robot by including mm.h
.../devicetree/bindings/display/ht16k33.txt| 42 ++
drivers/auxd
When requesting a trim for several bytes, everything up to the next
erase-group is erased. This causes data corruption.
Signed-off-by: Robin van der Gracht ro...@protonic.nl
---
drivers/mmc/core/core.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/mmc/core
occurred during masking.
This is unwanted behavior especially when using level triggered
interrupts. In this case every interrupt triggers twice. If the
interrupt is handled in the handler, the second interrupt will be
the first one to be able to ack the interrupt.
Signed-off-by: Robin van der Gracht
Signed-off-by: Robin van der Gracht ro...@protonic.nl
---
drivers/mmc/host/mxs-mmc.c | 37 +
1 file changed, 29 insertions(+), 8 deletions(-)
diff --git a/drivers/mmc/host/mxs-mmc.c b/drivers/mmc/host/mxs-mmc.c
index 073e871..efe8ae1 100644
--- a/drivers/mmc
van der Gracht
---
drivers/pwm/pwm-mxs.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/pwm/pwm-mxs.c b/drivers/pwm/pwm-mxs.c
index a53d309..7e1fa0a 100644
--- a/drivers/pwm/pwm-mxs.c
+++ b/drivers/pwm/pwm-mxs.c
@@ -10,6 +10,7 @@
*/
#include
+#include
#include
:
pwm: pwm-mxs: Wait for configuration to apply before disabling PWM
is more accurate?
Agreed
On Wed, Jun 19, 2013 at 01:51:26PM +0200, Robin van der Gracht wrote:
When disabling the pwm, the output state locks at its current state.
Please use the proper spelling "PWM" in
:
pwm: pwm-mxs: Wait for configuration to apply before disabling PWM
is more accurate?
Agreed
On Wed, Jun 19, 2013 at 01:51:26PM +0200, Robin van der Gracht wrote:
When disabling the pwm, the output state locks at its current state.
Please use the proper spelling PWM in prose.
Ok
van der Gracht ro...@protonic.nl
---
drivers/pwm/pwm-mxs.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/pwm/pwm-mxs.c b/drivers/pwm/pwm-mxs.c
index a53d309..7e1fa0a 100644
--- a/drivers/pwm/pwm-mxs.c
+++ b/drivers/pwm/pwm-mxs.c
@@ -10,6 +10,7 @@
*/
#include linux/clk.h
output period.
Signed-off-by: Robin van der Gracht
---
drivers/pwm/pwm-mxs.c |8
1 file changed, 8 insertions(+)
diff --git a/drivers/pwm/pwm-mxs.c b/drivers/pwm/pwm-mxs.c
index 3febddd..4ddc063 100644
--- a/drivers/pwm/pwm-mxs.c
+++ b/drivers/pwm/pwm-mxs.c
@@ -21,6 +21,7
output period.
Signed-off-by: Robin van der Gracht ro...@protonic.nl
---
drivers/pwm/pwm-mxs.c |8
1 file changed, 8 insertions(+)
diff --git a/drivers/pwm/pwm-mxs.c b/drivers/pwm/pwm-mxs.c
index 3febddd..4ddc063 100644
--- a/drivers/pwm/pwm-mxs.c
+++ b/drivers/pwm/pwm-mxs.c
@@ -21,6
host->base + LCDC_VDCTRL4);
clk_disable(host->clk);
--
1.5.6.5
Ping. Any comments on this?
Lothar Waßmann
I've encountered this problem to, and i can confirm your patch fixed it.
The VDCTRL4 register has no CLR feature.
Regards,
--
Robin van der Gracht
Protonic Holland.
tel.: +31 (0) 229
, host-base + LCDC_VDCTRL4);
clk_disable(host-clk);
--
1.5.6.5
Ping. Any comments on this?
Lothar Waßmann
I've encountered this problem to, and i can confirm your patch fixed it.
The VDCTRL4 register has no CLR feature.
Regards,
--
Robin van der Gracht
Protonic Holland.
tel.: +31 (0
for the boards mentioned before.
Reguards,
--
Robin van der Gracht
Protonic Holland.
tel.: +31 (0) 229 212928
fax.: +31 (0) 229 210930
Factorij 36 / 1689 AL Zwaag
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman
Hello,
Currently i'm writing a BSP for our new board. I quickly figured out
there are no
driver sections: hwmon and power. Why don't they exist (yet)?
Can i give a shot at creating them?
reguards,
--
Robin van der Gracht
Protonic Holland.
tel.: +31 (0) 229 212928
fax.: +31 (0) 229 210930
201 - 216 of 216 matches
Mail list logo
