files")
Signed-off-by: Martin Fuzzey
---
drivers/w1/mxc_w1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/mxc_w1.c b/drivers/w1/mxc_w1.c
index 8e6372f..3aeaaf5 100644
--- a/drivers/w1/mxc_w1.c
+++ b/drivers/w1/mxc_w1.c
@@ -17,8 +17,8 @@
* Martin Fuzzey
*/
ror: Can't force access to \"%s\"\n", name);
#else
return 0;
#endif
}
Fixes: 0f036bf4b87e ("env: Warn on force access if ENV_ACCESS_IGNORE_FORCE set")
Signed-off-by: Martin Fuzzey
---
env/flags.c | 5 +++--
1 file changed, 3 insertions(+)
Hi Robert,
On 16/10/2019 13:11, Robert Beckett wrote:
Huh, I had not seen that.
Martin's versions looks more complete than mine, so I would say go with
that one.
Martin: any objections to including your patches in here? I dont mind
pushing it through and handling any review comments etc. I am
if (ret) {
printf("%s: Error enabling phy supply\n", dev->name);
return ret;
Thanks for fixing this.
Tested-by: Martin Fuzzey
Regards,
Martin
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Hi Adam,
On 13/01/2019 15:00, Adam Ford wrote:
On Thu, Oct 4, 2018 at 12:55 PM Martin Fuzzey
wrote:
Configure the phy regulator if defined by the "phy-supply" DT phandle.
Signed-off-by: Martin Fuzzey
This patch seems to break the Ethernet on my board, but I think I have
a possibl
Hi Eugen,
On 27/11/2018 10:47, eugen.hris...@microchip.com wrote:
On 23.11.2018 11:53, Martin Fuzzey wrote:
Sometimes enumeration fails (about 1 in 50 times on my custom board).
The underlying reason is probably electrical but Linux does not have
the problem.
Comparing the Linux / u-boot
-boot fixes the problem.
Signed-off-by: Martin Fuzzey
---
drivers/w1/w1-uclass.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/w1/w1-uclass.c b/drivers/w1/w1-uclass.c
index 5544b19..ad86bf6 100644
--- a/drivers/w1/w1-uclass.c
+++ b/drivers/w1/w1-uclass.c
@@ -84,10 +84,6 @@ static
Signed-off-by: Martin Fuzzey
---
doc/device-tree-bindings/w1-eeprom/ds2502.txt | 33
drivers/w1-eeprom/Kconfig | 13 ++
drivers/w1-eeprom/Makefile| 1 +
drivers/w1-eeprom/ds2502.c| 244 ++
include/w1.h
Two variants of controllers are supported:
V1 (bitwise only) found in
i.MX21, i.MX27, i.MX31, i.MX51
V2 (byte operations) found in
i.MX25, i.MX35, i.MX50, i.MX53
Only tested on i.MX53 hardware but in both modes
(by modifying the device tree).
Signed-off-by: Martin Fuzzey
On 23/10/18 10:40, eugen.hris...@microchip.com wrote:
I tried as much as possible to decouple the W1 bus from the W1 EEPROM
memories. It is possible that we will have a different framework for
EEPROMs that will include both 1wire and i2c eeproms, and then the
interfacing would be pretty easy to
On 23/10/18 09:07, eugen.hris...@microchip.com wrote:
On 22.10.2018 19:51, Martin Fuzzey wrote:
Building with CONFIG_W1 and CONFIG_CMD_W1 but without CONFIG_W1_EEPROM
fails with
drivers/w1/w1-uclass.c:104: undefined reference to
`w1_eeprom_register_new_device'
cmd/w1.c:93
Hi Eugen,
On 23/10/18 09:05, eugen.hris...@microchip.com wrote:
On 22.10.2018 19:31, Martin Fuzzey wrote:
When the "w1 bus" command is used with no bus master present
a data abort may occur.
This is because uclass_first_device() returns zero, but sets the output
struct udevi
Building with CONFIG_W1 and CONFIG_CMD_W1 but without CONFIG_W1_EEPROM
fails with
drivers/w1/w1-uclass.c:104: undefined reference to
`w1_eeprom_register_new_device'
cmd/w1.c:93: undefined reference to `w1_eeprom_read_buf'
Fix this.
Signed-off-by: Martin Fuzzey
---
cmd/w1.c
he correct accessor is dev_get_parent_platdata() not
dev_get_platdata()
Signed-off-by: Martin Fuzzey
---
drivers/w1-eeprom/ds24xxx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1-eeprom/ds24xxx.c b/drivers/w1-eeprom/ds24xxx.c
index 56186e5..0967acc 100644
--- a/drivers
s expected by the callers.
Signed-off-by: Martin Fuzzey
---
drivers/w1/w1-uclass.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/w1/w1-uclass.c b/drivers/w1/w1-uclass.c
index aecf7fe..cb41b68 100644
--- a/drivers/w1/w1-uclass.c
+++ b/drivers/w1/w
Add a driver for the regulators in the the DA9063 PMIC.
Signed-off-by: Martin Fuzzey
---
drivers/power/regulator/Kconfig | 10 +
drivers/power/regulator/Makefile | 1 +
drivers/power/regulator/da9063.c | 395 +++
3 files changed, 406 insertions(+)
create
This adds the basic register access operations and child regulator
binding (if a regulator driver exists).
Signed-off-by: Martin Fuzzey
---
drivers/power/pmic/Kconfig | 7 +
drivers/power/pmic/Makefile | 1 +
drivers/power/pmic/da9063.c | 187 +++
include/power
Add basic support for the Dialog DA9063 PMIC.
Only the regulators are supported for the moment.
Also teach "pmic dump" to handle non contiguous register maps.
Martin Fuzzey (3):
pmic: allow dump command for non contiguous register maps
power: pmic: add driver for Dialog DA9063 PM
will then be displayed as '--' by pmic dump.
Use a single error code rather than any error code so that
we can distinguish between a hardware failure reading the PMIC
and a non implemented register known to the driver.
Signed-off-by: Martin Fuzzey
---
cmd/pmic.c | 12 ++--
1 file changed, 10
The DT property "phy-mode" already provides the transceiver type.
Use it so that we do not have to also set CONFIG_FEC_XCV_TYPE
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/drivers/net
Configure the phy regulator if defined by the "phy-supply" DT phandle.
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 20
drivers/net/fec_mxc.h | 3 +++
2 files changed, 23 insertions(+)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
ind
A few fixes and improvements for the FEC driver.
They are functionally independent but included in a series to avoid
conflicts if merged out of order as they touch the same files.
Martin Fuzzey (4):
net: dm: fec: Fix time unit error in phy-reset-duration
net: dm: fec: Fix phy-reset-duration
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
index a1295fc..163ae4c 100644
--- a/drivers/net/fec_mxc.c
+++ b/drivers/net/fec_mxc.c
@@ -1354,20 +1354,17 @@
The DT binding says that phy-reset-duration is in ms, but the driver
currently uses udelay().
Switch to mdelay() to fix this.
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
The DT property "phy-mode" already provides the transceiver type.
Use it so that we do not have to also set CONFIG_FEC_XCV_TYPE
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/drivers/net
Configure the phy regulator if defined by the "phy-supply" DT phandle.
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 20
drivers/net/fec_mxc.h | 3 +++
2 files changed, 23 insertions(+)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
ind
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
index a1295fc..163ae4c 100644
--- a/drivers/net/fec_mxc.c
+++ b/drivers/net/fec_mxc.c
@@ -1354,20 +1354,17 @@
The DT binding says that phy-reset-duration is in ms, but the driver
currently uses udelay().
Switch to mdelay() to fix this.
Signed-off-by: Martin Fuzzey
---
drivers/net/fec_mxc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
A few fixes and improvements for the FEC driver.
They are functionally independent but included in a series to avoid
conflicts if merged out of order as they touch the same files.
Martin Fuzzey (4):
net: dm: fec: Fix time unit error in phy-reset-duration
net: dm: fec: Fix phy-reset-duration
-by: Martin Fuzzey <mfuz...@parkeon.com>
Regards,
Martin
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Hi Mario,
thank you for your very quick reply.
On 01/03/18 09:01, Mario Six wrote:
Looks like that's it (from drivers/core/of_addr.c):
* Note: We consider that crossing any level with #size-cells == 0 to mean
* that translation is impossible (that is we are not dealing with a value
*
Hi,
since this commit:
commit f62ca2cd2ab8171f603960da9203ceb6ee8a1efd
Author: Mario Six
Date: Mon Jan 15 11:07:45 2018 +0100
gpio: pca953x_gpio: Make live-tree compatible
I am getting the error message "__of_translate_address: Bad cell count
for pcal6524@1"
I
albert.u.b...@aribaud.net wrote:
Hi Jagan,
On Wed, 16 Oct 2013 11:16:49 +0530, Jagan Teki
jagannadh.t...@gmail.com wrote:
Hi,
On Tue, Oct 15, 2013 at 11:27 PM, Martin Fuzzey mfuz...@parkeon.com wrote:
When writing buffers that are not 32 bit aligned data loss occurs.
This can also occur when
twice for the non
aligned case.
Signed-off-by: Martin Fuzzey mfuz...@parkeon.com
---
drivers/spi/mxc_spi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/mxc_spi.c b/drivers/spi/mxc_spi.c
index 859c43f..964a2b7 100644
--- a/drivers/spi/mxc_spi.c
+++ b/drivers
34 matches
Mail list logo