Leaving the mux enabled causes needless I2C traffic on the downstream
bus. De-selecting after every request causes excess I2C traffic and
switching.
This patch implements a hybrid solution: After 200ms of inactivity,
the mux is disabled.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
Leaving the mux enabled causes needless I2C traffic on the downstream
bus. De-selecting after every request causes excess I2C traffic and
switching.
This patch implements a hybrid solution: After 200ms of inactivity,
the mux is disabled.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
Leaving the mux enabled causes needless I2C traffic on the downstream
bus. De-selecting after every request causes excess I2C traffic and
switching.
This patch implements a hybrid solution: After 200ms of inactivity,
the mux is disabled.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
On 11/26/2013 10:06 AM, Wolfram Sang wrote:
On Tue, Nov 26, 2013 at 07:32:00AM +0100, Mike Looijmans wrote:
Leaving the mux enabled causes needless I2C traffic on the downstream
bus. De-selecting after every request causes excess I2C traffic and
switching.
This patch implements a hybrid
On 11/26/2013 01:28 PM, Wolfram Sang wrote:
CCing linux-pm, maybe they know more...
The extra I2C traffic consumes extra power. If the bus is terminated
using 2k resistors, approximately 1mA of current (assuming ~2V
signals) is flowing when the bus is pulled low. On low power
designs, this
to communicate via I2C for several seconds. With this patch, I2C
transactions will not be interrupted or otherwise halfway completed.
v2: Completely ignore signals.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/i2c/busses/i2c-davinci.c | 17 +
1 file changed, 9
from that
driver as well.
Cool, thanks!
Are you going to update the davinci patch as well?
An amended patch is on its way now. I forgot to set the subject to PATCHv2
though.
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH
When a board does not have the WP line wired at all, the card
may be detected as read-only. Add a quirk and a device property
to disable WP detection.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mmc/host/sdhci-pltfm.c |3 +++
drivers/mmc/host/sdhci.c |3
From: Mike Looijmans milo-softw...@users.sourceforge.net
Having a board where the I2C bus locks up occasionally made it clear
that the bus recovery in the i2c-davinci driver will only work on
some boards, because on regular boards, this will only toggle GPIO
lines that aren't muxed to the actual
logic level
the wp happens to think it's wired. I just want to be able to tell the driver
that the WP line is
free-floating-and-might-have-any-random-value-at-any-given-moment which is a
bit long, so I'd go for disable-wp instead.
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
If vmmc or vqmmc regulators are controlled by an I2C device, the
request for the regulator is likely to fail because the I2C bus has
not been probed yet. The sdhci then incorrectly assumes that the user
never wanted to use a regulator anyway and continues without ever
enabling or configuring the
On 03/09/2014 09:28 PM, Wolfram Sang wrote:
On Fri, Feb 28, 2014 at 11:32:05AM +0100, mike.looijm...@topic.nl wrote:
From: Mike Looijmans milo-softw...@users.sourceforge.net
Having a board where the I2C bus locks up occasionally made it clear
that the bus recovery in the i2c-davinci driver
a 2.6.37 kernel, and that's currently the
only board we have with an OMAP-L1.
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail
On 03/09/2014 09:21 PM, Wolfram Sang wrote:
On Thu, Jan 09, 2014 at 12:11:25PM +0100, Mike Looijmans wrote:
When a signal is caught while the i2c-davinci bus driver is transferring,
the drive just abandons the transfer and leaves the controller to fend
for itself. The next I2C transaction
Pressing CTRL-C while communicating with an I2C device leads to erratic
behaviour. The cause is that the controller will interrupt the I2C transfer
in progress, and leave the client device in an undefined state. Many
drivers do not handle error return codes on I2C transfers. The calling driver
has
On 03/11/2014 05:49 AM, Suneel Garapati wrote:
Hi Mike/Soren,
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail
on this topic:
http://lkml.org/lkml/2014/1/9/246
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/i2c/busses/i2c-cadence.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/i2c/busses/i2c-cadence.c b/drivers/i2c/busses/i2c-cadence.c
index
is SD0_WP_CD_SEL, and 0x002E sets CD to pin 46 and
WP to pin 0, not to EMIO as I specified in the design.
Eli: Maybe you have the same issue as Mike. Can you please check it?
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH
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
an I2C device in a loop and interrupting it
often resulted in a initiating i2c bus recovery storm and not being
able to communicate via I2C for several seconds. With this patch, the
userspace call simply returns EINTR and the next I2C transaction
succeeds without errors.
Signed-off-by: Mike Looijmans
On 26-3-2014 16:09, Georgi Djakov wrote:
On 03/07/2014 04:18 PM, Mike Looijmans wrote:
If vmmc or vqmmc regulators are controlled by an I2C device, the
request for the regulator is likely to fail because the I2C bus has
not been probed yet. The sdhci then incorrectly assumes that the user
never
If vmmc or vqmmc regulators are controlled by an I2C device, the
request for the regulator is likely to fail because the I2C bus has
not been probed yet. The sdhci then incorrectly assumes that the user
never wanted to use a regulator anyway and continues without ever
enabling or configuring the
that has an I2C regulator for one of the sdhcis
and no regulators at all for the other. This patch enables such a system
to work correctly.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mmc/host/sdhci.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff
that has an I2C regulator for one of the sdhcis
and no regulators at all for the other. This patch enables such a system
to work correctly.
v2: Do not change logging output
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mmc/host/sdhci.c |4
1 file changed, 4 insertions
On 04/07/2014 10:11 AM, Arnd Bergmann wrote:
On Monday 07 April 2014 08:38:28 Mike Looijmans wrote:
index 34aef81..43b90c1 100644
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -2972,6 +2972,8 @@ int sdhci_add_host(struct sdhci_host *host)
host-vqmmc
writing these DTS by hand which is not our case - at least
for majority of our customers.
I write them by hand. Is there any other way?
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 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
On 12/10/2014 10:34 AM, Lars-Peter Clausen wrote:
On 12/05/2014 01:37 PM, 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
Is this v3 patch okay or are you waiting for additional changes?
Kind regards,
Mike.
On 11/21/2014 10:40 AM, 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
for two frequencies. If the results are equal, or if the call returns
an error, the driver assumes the clock is fixed.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v3: Only enable clock once in hw_params which may be called multiple times.
sound/soc/adi/axi-spdif.c | 62
On 12/09/2014 07:48 PM, Mark Brown wrote:
On Tue, Dec 09, 2014 at 07:12:30PM +0100, Mike Looijmans wrote:
On 12/09/2014 05:14 PM, Mark Brown wrote:
If a regulator depends on another regulator that happens to be called
later, the kernel always prints a message like this:
reg-fixed-voltage
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 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
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
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 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
are equal, or if the call returns
an error, the driver assumes the clock is fixed.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v2: Fix fixed clock detection as discussed.
sound/soc/adi/axi-spdif.c | 60 -
1 file changed, 38 insertions(+), 22
Just a ping to ask for attention. Anyone care to review, comment or otherwise
provide some feedback?
On 12/04/2014 08:26 AM, Mike Looijmans wrote:
This driver supports the TI CDCE925 programmable clock synthesizer.
The chip contains two PLLs with spread-spectrum clocking support and
five
If the regulator cannot be registered because its supplier is not
available yet, don't write an error. There is no need to alert the
user of probe deferrals.
This fixes a storm of error messages at boot when a GPIO controlled
regulator is supplied by an I2C controlled supply.
Signed-off-by: Mike
the message to debug level.
This fixes a storm of error messages at boot when a board has a power
regulator on an I2C bus which powers GPIO controlled regulators for
example.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/regulator/core.c |2 +-
1 file changed, 1 insertion(+), 1
are errors.
--
Mike Looijmans
--
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 at http://www.tux.org/lkml/
Just a ping to inform if you've had had time to look at this?
Mike.
On 12/04/2014 08:26 AM, Mike Looijmans wrote:
This driver supports the TI CDCE925 programmable clock synthesizer.
The chip contains two PLLs with spread-spectrum clocking support and
five output dividers. The driver only
cause a reset.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v4: Fix 'return' with a value, in function returning void
.../devicetree/bindings/watchdog/gpio-wdt.txt |5 +++
drivers/watchdog/gpio_wdt.c| 37 +++-
2 files changed, 34
On 22-01-15 03:24, Sebastian Reichel wrote:
Hi,
On Tue, Oct 28, 2014 at 08:05:12AM +0100, 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
The driver reported 30% less than actually measured. This turned out to
be caused by a simple typo in the formula to calculate the LSB quantity.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/power/ltc2941-battery-gauge.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
On 12-01-15 04:04, Mike Turquette wrote:
On Thu, Jan 8, 2015 at 11:01 PM, Mike Looijmans mike.looijm...@topic.nl wrote:
Just a ping to inform if you've had had time to look at this?
Its in the queue for review this week. A lot to catch up on after the
holidays. Thanks for the ping.
Just
with the correct names for these chips.
This repairs the disappearance of NOR flash on the Miami boards since 3.18.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
drivers/mtd/devices/m25p80.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/devices/m25p80.c
Oops, arch/arm/boot/dts/topic-dyplo.dtsi should not have been in there. Will
send a v2 patch to correct that.
On 07-05-15 14:00, Mike Looijmans wrote:
When dma-coherent transfers are enabled, the mmap call must
not change the pg_prot flags in the vma struct.
Split the arm_dma_mmap
consistent in the
descriptions into coherent to be clear about this. Most hardware
will offer coherent memory, so the logical choice here is to adapt
the description to match reality.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
Documentation/DMA-API.txt | 27
, the mapped memory is cacheable and the
transfer speed is again 600MB/s (limited by the FPGA) when
the data is in the L2 cache, while data integrity is being
maintained.
The patch has no effect on non-coherent DMA.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v2: Mistakenly sent the wrong patch
, the mapped memory is cacheable and the
transfer speed is again 600MB/s (limited by the FPGA) when
the data is in the L2 cache, while data integrity is being
maintained.
The patch has no effect on non-coherent DMA.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
arch/arm/boot/dts/topic-dyplo.dtsi
, the mapped memory is cacheable and the
transfer speed is again 600MB/s (limited by the FPGA) when
the data is in the L2 cache, while data integrity is being
maintained.
The patch has no effect on non-coherent DMA.
Signed-off-by: Mike Looijmans mike.looijm...@topic.nl
---
v2: Mistakenly sent the wrong patch
On 02-06-15 09:50, Paul Bolle wrote:
On Mon, 2015-06-01 at 12:13 +0200, Mike Looijmans wrote:
--- /dev/null
+++ b/drivers/clk/clk-cdce925.c
+static int cdce925_regmap_i2c_write(
+ void *context, const void *data, size_t count)
+ dev_dbg(i2c-dev, %s(%u) %#x %#x\n, __func__
On 02-06-15 09:50, Paul Bolle wrote:
On Mon, 2015-06-01 at 12:13 +0200, Mike Looijmans wrote:
--- /dev/null
+++ b/drivers/clk/clk-cdce925.c
+static int cdce925_regmap_i2c_write(
+ void *context, const void *data, size_t count)
+ dev_dbg(i2c-dev, %s(%u) %#x %#x\n, __func__
Ping!
Just curious, any further feedback or comment after Arnd Bergmann's ack?
It fixes a bug that took quite some time to discover and analyze, we should
save other people going through that same trouble.
On 07-05-15 14:54, Mike Looijmans wrote:
When dma-coherent transfers are enabled
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
v3: Remove clk
1 - 100 of 552 matches
Mail list logo
