On 12/04/2014 01:45 PM, Lars-Peter Clausen wrote:
On 12/04/2014 07:52 AM, Mike Looijmans wrote:
If the master clock supports programmable rates, program it to generate
the desired frequency. Only apply constraints when the clock is fixed.
This allows proper clock generation for both 44100
On 12/04/2014 01:45 PM, Lars-Peter Clausen wrote:
On 12/04/2014 07:52 AM, Mike Looijmans wrote:
If the master clock supports programmable rates, program it to generate
the desired frequency. Only apply constraints when the clock is fixed.
This allows proper clock generation for both 44100
and Y3 derive from PLL1
Y4 and Y5 derive from PLL2
Given a target output frequency, the driver will set the PLL and
divider to best approximate the desired output.
Signed-off-by: Mike Looijmans
---
v2: Coding style check
Add devicetree binding documentation
.../devicetree/bindings/clock
ams first.
Starting the clock and enabling the SPDIF output AFTER programming the
dividers is a more logical order anyway.
Signed-off-by: Mike Looijmans
---
sound/soc/adi/axi-spdif.c | 56 -
1 file changed, 35 insertions(+), 21 deletions(-)
diff --git
and enabling the SPDIF output AFTER programming the
dividers is a more logical order anyway.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
sound/soc/adi/axi-spdif.c | 56 -
1 file changed, 35 insertions(+), 21 deletions(-)
diff --git
and Y3 derive from PLL1
Y4 and Y5 derive from PLL2
Given a target output frequency, the driver will set the PLL and
divider to best approximate the desired output.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v2: Coding style check
Add devicetree binding documentation
On 24-11-2014 14:15, Grygorii Strashko wrote:
Hi Uwe,
On 11/23/2014 07:04 PM, Uwe Kleine-König wrote:
On Thu, Nov 20, 2014 at 12:03:08PM +0200, Grygorii Strashko wrote:
@@ -664,6 +759,7 @@ static int davinci_i2c_probe(struct platform_device *pdev)
if
one other module uses it (xylon_connector.c).
Signed-off-by: Mike Looijmans
---
drivers/gpu/drm/drm_sysfs.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c
index ab1a5f6..d0296cc 100644
--- a/drivers/gpu/drm/drm_sysfs.c
+++ b/drive
uses it (xylon_connector.c).
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/gpu/drm/drm_sysfs.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c
index ab1a5f6..d0296cc 100644
--- a/drivers/gpu/drm/drm_sysfs.c
On 24-11-2014 14:15, Grygorii Strashko wrote:
Hi Uwe,
On 11/23/2014 07:04 PM, Uwe Kleine-König wrote:
On Thu, Nov 20, 2014 at 12:03:08PM +0200, Grygorii Strashko wrote:
@@ -664,6 +759,7 @@ static int davinci_i2c_probe(struct platform_device *pdev)
if
ether a timeout must also cause a reset.
Signed-off-by: Mike Looijmans
---
v3: Indentation adjusted to match
Fix error path in probe when notification registration fails
Prevent double assignment of "armed" variable
.../devicetree/bindings/watchdog/gpio-wdt.txt |5 ++
cause a reset.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v3: Indentation adjusted to match
Fix error path in probe when notification registration fails
Prevent double assignment of armed variable
.../devicetree/bindings/watchdog/gpio-wdt.txt |5 +++
drivers/watchdog
On 11/21/2014 08:28 AM, Guenter Roeck wrote:
On 11/20/2014 10:53 PM, Mike Looijmans wrote:
On some chips, like the TPS386000, the trigger cannot be disabled
and the CPU must keep toggling the line at all times. Add a switch
"always_running" to keep toggling the GPIO line
ether a timeout must also cause a reset.
Signed-off-by: Mike Looijmans
---
v2: Rename property "always_running" to "always-running" and add devicetree
documentation
.../devicetree/bindings/watchdog/gpio-wdt.txt |5 +
drivers/watchdog/gpio_wdt.c
ether a timeout must also cause a reset.
Signed-off-by: Mike Looijmans
---
drivers/watchdog/gpio_wdt.c | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/watchdog/gpio_wdt.c b/drivers/watchdog/gpio_wdt.c
index 220a9e0..921ee67 100644
--- a/drivers
cause a reset.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/watchdog/gpio_wdt.c | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/watchdog/gpio_wdt.c b/drivers/watchdog/gpio_wdt.c
index 220a9e0..921ee67 100644
--- a/drivers
cause a reset.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v2: Rename property always_running to always-running and add devicetree
documentation
.../devicetree/bindings/watchdog/gpio-wdt.txt |5 +
drivers/watchdog/gpio_wdt.c| 20
On 11/21/2014 08:28 AM, Guenter Roeck wrote:
On 11/20/2014 10:53 PM, Mike Looijmans wrote:
On some chips, like the TPS386000, the trigger cannot be disabled
and the CPU must keep toggling the line at all times. Add a switch
always_running to keep toggling the GPIO line regardless of the
state
have to
trigger an I2C error at exactly the moment that a clock frequency change is
about to occur...).
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
have to
trigger an I2C error at exactly the moment that a clock frequency change is
about to occur...).
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
On 11/04/2014 08:47 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 02:35:50PM +0100, Mike Looijmans wrote:
I still need help with one thing that isn't clear to me though. The DT is
parsed when calling regulator_register. But then how do I fetch my "private"
settings in th
On 11/04/2014 09:26 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 07:50:45AM +0100, Mike Looijmans wrote:
v3: Add .of_match_table and prefix lltc
Clarify why regmap cannot be used
Add lltc,operating-mode (0..3) DT property
regulator child nodes are optional
Leave out the mode
On 11/04/2014 09:26 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 07:50:45AM +0100, Mike Looijmans wrote:
v3: Add .of_match_table and prefix lltc
Clarify why regmap cannot be used
Add lltc,operating-mode (0..3) DT property
regulator child nodes are optional
Leave out the mode
On 11/04/2014 08:47 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 02:35:50PM +0100, Mike Looijmans wrote:
I still need help with one thing that isn't clear to me though. The DT is
parsed when calling regulator_register. But then how do I fetch my private
settings in there BEFORE the regulator
On 11/04/2014 12:34 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 09:55:14AM +0100, Mike Looijmans wrote:
On 11/03/2014 06:38 PM, Mike Looijmans wrote:
You need to develop against current versions of the kernel, this is
something that was merged into Linus' tree during the merge window
On 11/04/2014 12:34 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 09:55:14AM +0100, Mike Looijmans wrote:
On 11/03/2014 06:38 PM, Mike Looijmans wrote:
You need to develop against current versions of the kernel, this is
something that was merged into Linus' tree during the merge window
On 11/03/2014 06:38 PM, Mike Looijmans wrote:
On 3-11-2014 16:10, Mark Brown wrote:
On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote:
On 11/03/2014 01:09 PM, Mark Brown wrote:
No function calls, just use regulators_node. What is unclear about the
functionality?
I don't
On 11/03/2014 06:38 PM, Mike Looijmans wrote:
On 3-11-2014 16:10, Mark Brown wrote:
On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote:
On 11/03/2014 01:09 PM, Mark Brown wrote:
No function calls, just use regulators_node. What is unclear about the
functionality?
I don't
On 11/04/2014 12:34 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 09:55:14AM +0100, Mike Looijmans wrote:
On 11/03/2014 06:38 PM, Mike Looijmans wrote:
You need to develop against current versions of the kernel, this is
something that was merged into Linus' tree during the merge window
On 11/04/2014 12:34 PM, Mark Brown wrote:
On Tue, Nov 04, 2014 at 09:55:14AM +0100, Mike Looijmans wrote:
On 11/03/2014 06:38 PM, Mike Looijmans wrote:
You need to develop against current versions of the kernel, this is
something that was merged into Linus' tree during the merge window
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
Signed-off-by: Mike Looijmans
---
v3: Add .of_match_table and prefix lltc
Clarify why regmap cannot be used
Add lltc,operating-mode (0..3) DT property
regulator child nodes are optional
.../devicetree
On 3-11-2014 16:10, Mark Brown wrote:
On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote:
On 11/03/2014 01:09 PM, Mark Brown wrote:
No function calls, just use regulators_node. What is unclear about the
functionality?
I don't understand what you mean by "regulators
On 11/03/2014 01:09 PM, Mark Brown wrote:
On Mon, Nov 03, 2014 at 09:10:08AM +0100, Mike Looijmans wrote:
On 10/30/2014 05:51 PM, Mark Brown wrote:
+ np_child = of_get_child_by_name(np_regulators,
+ ltc3562_regulators[i].name
On 10/30/2014 05:51 PM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 12:26:55PM +0100, Mike Looijmans wrote:
+ np = of_node_get(i2c->dev.of_node);
+ np_regulators = of_get_child_by_name(np, "regulators");
+ np_child = of_get_child_by_name(
On 10/30/2014 05:51 PM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 12:26:55PM +0100, Mike Looijmans wrote:
+ np = of_node_get(i2c-dev.of_node);
+ np_regulators = of_get_child_by_name(np, regulators);
+ np_child = of_get_child_by_name(np_regulators
On 11/03/2014 01:09 PM, Mark Brown wrote:
On Mon, Nov 03, 2014 at 09:10:08AM +0100, Mike Looijmans wrote:
On 10/30/2014 05:51 PM, Mark Brown wrote:
+ np_child = of_get_child_by_name(np_regulators,
+ ltc3562_regulators[i].name
On 3-11-2014 16:10, Mark Brown wrote:
On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote:
On 11/03/2014 01:09 PM, Mark Brown wrote:
No function calls, just use regulators_node. What is unclear about the
functionality?
I don't understand what you mean by regulators_node
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v3: Add .of_match_table and prefix lltc
Clarify why regmap cannot be used
Add lltc,operating-mode (0..3) DT property
regulator child nodes
On 30-10-2014 17:51, Mark Brown wrote:
On Thu, Oct 30, 2014 at 12:26:55PM +0100, Mike Looijmans wrote:
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
v2: Prefix "lltc" to devicetree properties. Use the same property names
as the ltc3589 driver. Remo
On 30-10-2014 17:51, Mark Brown wrote:
On Thu, Oct 30, 2014 at 12:26:55PM +0100, Mike Looijmans wrote:
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
v2: Prefix lltc to devicetree properties. Use the same property names
as the ltc3589 driver. Remove default
On 10/30/2014 11:58 AM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 11:53:37AM +0100, Mike Looijmans wrote:
On 10/30/2014 11:29 AM, Mike Looijmans wrote:
So I should add "regulator-default-voltage" to the generic code? That would
indeed be better than trying to do it into t
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
v2: Prefix "lltc" to devicetree properties. Use the same property names
as the ltc3589 driver. Remove default-voltage property. Use
devm_register_regulator.
Signed-off-by: Mike Looijmans
---
.../
On 10/30/2014 11:29 AM, Mike Looijmans wrote:
On 10/30/2014 11:15 AM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 07:47:44AM +0100, Mike Looijmans wrote:
On 10/29/2014 01:30 PM, Mark Brown wrote:
A couple of problems here:
- This contains DT code but no DT bindings documentation
On 10/30/2014 11:15 AM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 07:47:44AM +0100, Mike Looijmans wrote:
On 10/29/2014 01:30 PM, Mark Brown wrote:
A couple of problems here:
- This contains DT code but no DT bindings documentation; the binding
documentation is mandatory for any
On 10/29/2014 01:30 PM, Mark Brown wrote:
On Wed, Oct 29, 2014 at 09:16:00AM +0100, Mike Looijmans wrote:
+ if (!status->voltage_set) {
+ if (of_property_read_u32(dev->dev.of_node,
+ "ltc3562-default-voltage", _default) == 0) {
A co
On 10/29/2014 01:30 PM, Mark Brown wrote:
On Wed, Oct 29, 2014 at 09:16:00AM +0100, Mike Looijmans wrote:
+ if (!status-voltage_set) {
+ if (of_property_read_u32(dev-dev.of_node,
+ ltc3562-default-voltage, v_default) == 0) {
A couple of problems
On 10/30/2014 11:15 AM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 07:47:44AM +0100, Mike Looijmans wrote:
On 10/29/2014 01:30 PM, Mark Brown wrote:
A couple of problems here:
- This contains DT code but no DT bindings documentation; the binding
documentation is mandatory for any
On 10/30/2014 11:29 AM, Mike Looijmans wrote:
On 10/30/2014 11:15 AM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 07:47:44AM +0100, Mike Looijmans wrote:
On 10/29/2014 01:30 PM, Mark Brown wrote:
A couple of problems here:
- This contains DT code but no DT bindings documentation
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
v2: Prefix lltc to devicetree properties. Use the same property names
as the ltc3589 driver. Remove default-voltage property. Use
devm_register_regulator.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
On 10/30/2014 11:58 AM, Mark Brown wrote:
On Thu, Oct 30, 2014 at 11:53:37AM +0100, Mike Looijmans wrote:
On 10/30/2014 11:29 AM, Mike Looijmans wrote:
So I should add regulator-default-voltage to the generic code? That would
indeed be better than trying to do it into this driver
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
Signed-off-by: Mike Looijmans
---
drivers/regulator/Kconfig |7 +
drivers/regulator/Makefile |1 +
drivers/regulator/ltc3562.c | 387 +++
3 files changed, 395
This patch adds the LTC3562 I2C controlled voltage regulator to
the kernel. The driver was tested and developed on a Topic Miami
board where this chip supplies the IO voltages for the FPGA pins.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This patch adds the LTC3562 I2C controlled voltage regulator to
the kernel. The driver was tested and developed on a Topic Miami
board where this chip supplies the IO voltages for the FPGA pins.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
The ltc3562 is an I2C controlled regulator supporting 4 independent
outputs.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/regulator/Kconfig |7 +
drivers/regulator/Makefile |1 +
drivers/regulator/ltc3562.c | 387 +++
3
As discussed here, I'll post a new patch which simply removes the error
messages.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
sdhci_add_host and sdhci_platfm_init already report failure,
so don't emit error messages when a failure occurs. This prevents
occurences of "deferred" messages when required power supplies
are not ready for operation yet.
Signed-off-by: Mike Looijmans
---
drivers/mmc/host/sdhci-o
On 10/27/2014 05:38 PM, Sebastian Reichel wrote:
Hi,
On Thu, Oct 23, 2014 at 02:38:38PM +0200, Mike Looijmans wrote:
Both the LTC2941 and LTC2943 measure battery capacity.
The LTC2943 is compatible with the LTC2941, it adds voltage and
temperature monitoring, and uses a slightly different
This adds the devicetree binding documentation for the LTC2941 and LTC2943
driver. These are I2C connected battery gas gauge ICs.
Signed-off-by: Mike Looijmans
---
.../devicetree/bindings/power/ltc2941.txt | 27
1 file changed, 27 insertions(+)
create mode
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
v3: Correctly set configuration register. Allow negative values
for the sense resistor.
v4: Run checkpatch.pl and fix all errors and warnings.
v5: Prefix "lltc," to devicetree properties.
Signed-off-by: Mike
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
v3: Correctly set configuration register. Allow negative values
for the sense resistor.
v4: Run checkpatch.pl and fix all errors and warnings.
v5: Prefix lltc, to devicetree properties.
Signed-off-by: Mike Looijmans mike.looijm
This adds the devicetree binding documentation for the LTC2941 and LTC2943
driver. These are I2C connected battery gas gauge ICs.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
.../devicetree/bindings/power/ltc2941.txt | 27
1 file changed, 27
On 10/27/2014 05:38 PM, Sebastian Reichel wrote:
Hi,
On Thu, Oct 23, 2014 at 02:38:38PM +0200, Mike Looijmans wrote:
Both the LTC2941 and LTC2943 measure battery capacity.
The LTC2943 is compatible with the LTC2941, it adds voltage and
temperature monitoring, and uses a slightly different
sdhci_add_host and sdhci_platfm_init already report failure,
so don't emit error messages when a failure occurs. This prevents
occurences of deferred messages when required power supplies
are not ready for operation yet.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mmc/host
As discussed here, I'll post a new patch which simply removes the error
messages.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
and Y3 derive from PLL1
Y4 and Y5 derive from PLL2
Given a target output frequency, the driver will set the PLL and
divider to best approximate the desired output.
Signed-off-by: Mike Looijmans
---
drivers/clk/Kconfig | 17 +
drivers/clk/Makefile |1 +
drivers/clk/clk-cdce925.c
This patch contains a driver for an I2C controlled clock synthesizer.
We've been using this driver for a while for creating clock signals
for HDMI and audio.
The only thing missing in this patch is the devicetree binding
information, I intend to add that in a later patch.
Please
This patch contains a driver for an I2C controlled clock synthesizer.
We've been using this driver for a while for creating clock signals
for HDMI and audio.
The only thing missing in this patch is the devicetree binding
information, I intend to add that in a later patch.
Please
and Y3 derive from PLL1
Y4 and Y5 derive from PLL2
Given a target output frequency, the driver will set the PLL and
divider to best approximate the desired output.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/clk/Kconfig | 17 +
drivers/clk/Makefile |1
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
v3: Correctly set configuration register. Allow negative values
for the sense resistor.
v4: Run checkpatch.pl and fix all errors and warnings.
Signed-off-by: Mike Looijmans
---
drivers/power/Kconfig |8
When the error code is -EPROBE_DEFER, this will already be reported
so don't emit an error message in that case.
Signed-off-by: Mike Looijmans
---
drivers/mmc/host/sdhci-of-arasan.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/sdhci-of-arasan.c
"ret" is a signed int, so use "%d" in format strings instead of "%u".
This prevents cryptic codes in error messages like this:
sdhci-arasan e0101000.sdhci: platform register failed (4294966779)
Signed-off-by: Mike Looijmans
Reviewed-by: Michal Simek
---
driv
ret is a signed int, so use %d in format strings instead of %u.
This prevents cryptic codes in error messages like this:
sdhci-arasan e0101000.sdhci: platform register failed (4294966779)
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
Reviewed-by: Michal Simek michal.si...@xilinx.com
When the error code is -EPROBE_DEFER, this will already be reported
so don't emit an error message in that case.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mmc/host/sdhci-of-arasan.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
v3: Correctly set configuration register. Allow negative values
for the sense resistor.
v4: Run checkpatch.pl and fix all errors and warnings.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/power/Kconfig
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
v3: Correctly set configuration register. Allow negative values
for the sense resistor.
Signed-off-by: Mike Looijmans
---
drivers/power/Kconfig |7 +
drivers/power/Makefile|1 +
drivers
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
v3: Correctly set configuration register. Allow negative values
for the sense resistor.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/power/Kconfig |7 +
drivers/power/Makefile
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
Signed-off-by: Mike Looijmans
---
drivers/power/Kconfig |7 +
drivers/power/Makefile|1 +
drivers/power/ltc2941-battery-gauge.c | 497 +
3 files changed, 505
client/driver for the Linear Technology LTC2941 and LTC2943
+ * Battery Gas Gauge IC
+ *
+ * Copyright (C) 2014 Topic Embedded Systems
+ *
+ * Author: Auryn Verwegen
+ * Author: Mike Looijmans
+ */
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#i
for the Linear Technology LTC2941 and LTC2943
+ * Battery Gas Gauge IC
+ *
+ * Copyright (C) 2014 Topic Embedded Systems
+ *
+ * Author: Auryn Verwegen
+ * Author: Mike Looijmans
+ */
+#include linux/kernel.h
+#include linux/module.h
+#include linux/types.h
+#include linux/errno.h
+#include linux
of LTC294X.
v2: Fix units of measurement: uV, uA and centidegrees.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/power/Kconfig |7 +
drivers/power/Makefile|1 +
drivers/power/ltc2941-battery-gauge.c | 497
I based this patch on the 3.17rc5 state. Hope this applies cleanly now?
On 09/15/2014 12:06 PM, Mike Looijmans wrote:
The KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577
("net/phy: micrel: Disable asymm
Pause flag for the KSZ9031 to fix this.
Signed-off-by: Mike Looijmans
---
drivers/net/phy/micrel.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
index fd0ea7c..011dbda 100644
--- a/drivers/net/phy/micrel.c
+++ b/drive
On 09/13/2014 12:18 AM, David Miller wrote:
From: Mike Looijmans
Date: Fri, 12 Sep 2014 14:40:37 +0200
The KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577
("net/phy: micrel: Disable asymmetric
On 09/13/2014 12:18 AM, David Miller wrote:
From: Mike Looijmans mike.looijm...@topic.nl
Date: Fri, 12 Sep 2014 14:40:37 +0200
The KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577
(net/phy: micrel: Disable
for the KSZ9031 to fix this.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/net/phy/micrel.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
index fd0ea7c..011dbda 100644
--- a/drivers/net/phy/micrel.c
I based this patch on the 3.17rc5 state. Hope this applies cleanly now?
On 09/15/2014 12:06 PM, Mike Looijmans wrote:
The KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577
(net/phy: micrel: Disable asymmetric
Pause flag for the KSZ9031 to fix this.
Signed-off-by: Mike Looijmans
---
drivers/net/phy/micrel.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
index 5a8993b..a932a35 100644
--- a/drivers/net/phy/micrel.c
+++ b/drive
On 09/11/2014 08:41 PM, Florian Fainelli wrote:
On 09/11/2014 06:45 AM, Mike Looijmans wrote:
Our KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577,
you have to unplug the cable and plug it back to get it to work
On 09/11/2014 08:41 PM, Florian Fainelli wrote:
On 09/11/2014 06:45 AM, Mike Looijmans wrote:
Our KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577,
you have to unplug the cable and plug it back to get it to work
for the KSZ9031 to fix this.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/net/phy/micrel.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
index 5a8993b..a932a35 100644
--- a/drivers/net/phy/micrel.c
Our KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577,
you have to unplug the cable and plug it back to get it to work.
Remove the SUPPORTED_Asym_Pause flag for the KSZ9031 to fix this.
Signed-off-by: Mike
Our KSZ9031 appears to suffer from the same hardware bug as described
for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577,
you have to unplug the cable and plug it back to get it to work.
Remove the SUPPORTED_Asym_Pause flag for the KSZ9031 to fix this.
Signed-off-by: Mike
or reliability.
Tested on a custom board with an OMAP-L138 CPU. Patch originally applied
to a 2.6.37 kernel and ported to 3.14.
Signed-off-by: Mike Looijmans
---
drivers/mmc/host/davinci_mmc.c | 52 +---
1 file changed, 33 insertions(+), 19 deletions(-)
diff
Note: I have not been able to test or even compile this on recent
kernels. Can somebody verify that this does not kill the SD driver?
Mike.
On 08/29/2014 08:41 AM, Mike Looijmans wrote:
The davinci-mmc driver uses a busy wait loop to wait for the card to
become ready (BUSY signal). The MMC
Note: I have not been able to test or even compile this on recent
kernels. Can somebody verify that this does not kill the SD driver?
Mike.
On 08/29/2014 08:41 AM, Mike Looijmans wrote:
The davinci-mmc driver uses a busy wait loop to wait for the card to
become ready (BUSY signal). The MMC
or reliability.
Tested on a custom board with an OMAP-L138 CPU. Patch originally applied
to a 2.6.37 kernel and ported to 3.14.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mmc/host/davinci_mmc.c | 52 +---
1 file changed, 33 insertions
s correct. All your remarks were. Problem currently is
that I'm not assigned to a project related to the davinci so I cannot
spend time to fix and port it (the actual platform still runs 2.6.37).
Feel free to adap my patch or comments and commit. Or wait a few weeks
for when I have a sponsor
not assigned to a project related to the davinci so I cannot
spend time to fix and port it (the actual platform still runs 2.6.37).
Feel free to adap my patch or comments and commit. Or wait a few weeks
for when I have a sponsor to split and update the patch.
--
Mike Looijmans
--
To unsubscribe
On 04/07/2014 02:51 PM, Arnd Bergmann wrote:
On Monday 07 April 2014 14:32:20 Mike Looijmans wrote:
On 04/07/2014 02:25 PM, Arnd Bergmann wrote:
Judging from the kernel output, regulator_get_optional returns -ENODEV if the
supply wasn't found.
Maybe the API is confusing (or wrong?) here
On 04/07/2014 02:25 PM, Arnd Bergmann wrote:
On Monday 07 April 2014 13:18:54 Ben Dooks wrote:
On 07/04/14 13:16, Ben Dooks wrote:
On 07/04/14 13:09, Mike Looijmans wrote:
On 04/07/2014 10:11 AM, Arnd Bergmann wrote:
On Monday 07 April 2014 08:38:28 Mike Looijmans wrote:
index 34aef81
401 - 500 of 552 matches
Mail list logo
