Tree source code, if it can be useful.
Best wishes.
--
Igor Plyatov
13.05.2019 18:39, Igor Plyatov пишет:
Dear developers,
can you please explain who must configure AT91SAM9G20 SOC pads to
operate as USB Host port? Is it AT91Bootstrap, U-Boot bootloader,
Linux kernel or this is not required at
Dear Robin,
Hi Igor,
Did you meet any issue with my latest patch?
sorry, but unfortunately I have no time to test it.
I have switched to PIO mode and continue other development.
Maybe later I will find time to test DMA mode, but not sure when.
Thank you for support!
--
Igor
of i.MX6 SOC and hardly broken eCSPI interface
number can change from SOC chip to chip.
Do you have any idea how to improve situation with eCSPI in DMA mode?
Best wishes.
--
Igor Plyatov
lopers.
Does first digit means "DMA request/event ID"? Where to find more info
about this?
Does second digit means "enum sdma_peripheral_type"?
Does third digit means "enum imx_dma_prio"?
Where can I find description of differenc
ame result as from my previous email.
Looks as you use either different GIT branch of kernel or you have
forget to say me about some patch.
Best wishes.
--
Igor Plyatov
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 5f3c1378b90e..908507fa9526 100644
--- a/drivers/dma/im
this
issue again?
Best wishes.
--
Igor Plyatov
Dear Uwe,
On Thu, Mar 28, 2019 at 10:04:21AM +0300, Igor Plyatov wrote:
Dear Uwe,
Hello Igor,
On Wed, Mar 27, 2019 at 08:40:00PM +0300, Igor Plyatov wrote:
please, help to resolve two issues with SPI DMA transfers at i.MX6Q
platform.
First issue is
[ 4465.008003] spi_master spi0: I/O
in DMA TX
[ 94.233788] spidev spi4.0: SPI transfer failed: -110
[ 94.238837] spi_master spi4: failed to transfer one message from queue
can't send spi message: Connection timed out
Aborted (core dumped)
Best wishes.
--
Igor Plyatov
Hi Igor,
Please have a try with the attache
Dear Uwe,
Hello Igor,
On Wed, Mar 27, 2019 at 08:40:00PM +0300, Igor Plyatov wrote:
please, help to resolve two issues with SPI DMA transfers at i.MX6Q
platform.
First issue is
[ 4465.008003] spi_master spi0: I/O Error in DMA RX
Second issue is duplication for one of received bytes
).
Looks like, ecspi5 has some different configuration in SPI or SDMA
drivers or bug in SDMA script.
Any ideas?
Best wishes.
--
Igor Plyatov
A8 64 20 26 87 54 06 F8 3B B1 72 36 23 40 0C B1 E9 C4 15 06 37
EE 28 B2 F2 C0 27 64 A9 36 42 |..d &.T..;.r6#@..7.(...'d.6B|
RX | 51 9B 62 77 22 B6 7D 1A F1 2E 8D 28 52 CD 34 03 B6 F8 18 BD 30 06
E5 E2 F9 A5 0A 5D 4E 40 9F 9F |Q.bw".}(R.4.0..]N@..|
RX | DB 02 16 FD B8 93 18 AA C2 A5 D2 14 72 06 17 28 FF 30 E5 2F 36 CA
11 2F 70 1B 8C BE 5C 2C 5E 37 |r..(.0./6../p...\,^7|
RX | 2E 74 35 E6 08 4D 90 CA F2 62 DE 64 69 F5 8C 68 25 72 97 5C 3C A8
8B AC C4 18 6B 20 44 C9 57 72 |.t5..M...b.di..h%r.\<.k D.Wr|
RX | 3D 8C 58 45 D9 E9 0F CB 4B ED 2F B4 E3 BC 1C 08 2E B3 64 6A 5C F0
17 20 08 82 40 4C 4B 97 BE 88 |=.XEK./...dj\.. ..@LK...|
RX | 24 16 CE FD FF DD C9 4B CB F8 FF AE B4 1C B6 E2 CF 1B 4D 2B 0B 64
4B 13 E6 8B 5F 31 23 1D B9 47 |$..K..M+.dK..._1#..G|
Best wishes.
--
Igor Plyatov
le is "/sys/class/rtc/rtcX/name" file, which
contains driver name.
For x86 and MC146818-compatible RTC its name is "rtc_cmos". And it can
be used to distinguish RTC type by hwclock utility.
Best wishes.
--
Igor Plyatov
est wishes.
--
Igor Plyatov
On 2018-02-19 07:40, Igor Plyatov wrote:
Hi!
I have board based on AT91SAM9G20 (ARM926EJ-S CPU), Linux-4.9.36 kernel
and RTC chip DS1340 (rtc-ds1307.c driver).
RTC chip connected by means of I2C-bus, without HW IRQ line connected.
Kernel configured to not us
g in the hwclock, or kernel bug or I have missed
something else?
Best wishes.
--
Igor Plyatov
speeds above 6 MHz. I
see corruption in data received by Linux and SPI overruns when OS has
big CPI and IO load.
Old kernel works fine at 22 MHz with the same device driver and hardware.
Can somebody comment and/or help on how to resolve this issue?
Best wishes.
--
Igor Plyatov
For those, who
above 6 MHz. I see
corruption in data received by Linux and SPI overruns when OS has big
CPI and IO load.
Old kernel works fine at 22 MHz with the same device driver and hardware.
Can somebody comment and/or help on how to resolve this issue?
Best wishes.
--
Igor Plyatov
ally big lags if OS has
some load. These lags are not acceptable for our high speed DSP.
Best wishes.
--
Igor Plyatov
e3948>] (start_kernel) from [<90008078>] (0x90008078)
---[ end trace 3da0cc3c43e8a19f ]---
mmcblk0: error -110 sending stop command, original cmd response 0x0,
card status 0x400900
mmcblk0: error -110 transferring data, sector 0, nr 8, cmd response 0x0,
card status 0x0
blk_update_re
improved to acquire ENERGYON bit. Its previous
algorythm still not reliable on 100 % and sometimes skip cable plugging.
Signed-off-by: Igor Plyatov
---
drivers/net/phy/smsc.c | 31 +++
1 file changed, 19 insertions(+), 12 deletions(-)
diff --git a/drivers/net/phy
.
* The Energy Detect Power-Down mode enabled again in the end of
procedure to
* save approximately 220 mW of power if cable is unplugged.
*/
Nice. Only one nitpick: ... _is_ enabled again...
Changed in [PATCH v3].
Best wishes.
--
Igor Plyatov
--
To unsubscribe from this list: send the line
metimes skip cable plugging.
>
> Signed-off-by: Igor Plyatov
> ---
> drivers/net/phy/smsc.c | 15 ---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/phy/smsc.c b/drivers/net/phy/smsc.c
> index c0f6479..8559ff1 100644
>
Dear David and Joe,
thank you for patch review!
Please look at email with subject
"[PATCH v2] net: phy: workaround for buggy cable detection by LAN8700
after cable plugging"
Best wishes.
--
Igor Plyatov
From: Joe Perches
Date: Thu, 13 Aug 2015 10:15:15 -0700
On Thu, 2015-08-1
improved to acquire ENERGYON bit. Its previous
algorythm still not reliable on 100 % and sometimes skip cable plugging.
Signed-off-by: Igor Plyatov
---
drivers/net/phy/smsc.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/drivers/net/phy/smsc.c b/drivers
Dear Joe,
On Thu, 2015-08-13 at 16:12 +0300, Igor Plyatov wrote:
* Due to HW bug, LAN8700 sometimes does not detect presence of energy in the
Ethernet cable in Energy Detect Power-Down mode (e.g while EDPWRDOWN bit is
set, the ENERGYON bit does not asserted sometimes). This is a common
improved to acquire ENERGYON bit. Its previous
algorythm still not reliable on 100 % and sometimes skip cable plugging.
Signed-off-by: Igor Plyatov
---
drivers/net/phy/smsc.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/drivers/net/phy/smsc.c b/drivers
after 10-20 unplugging/plugging.
The issue was tested and exists on kernels from linux-3.8.5 till current
linux-4.2-rc4-cbfe8fa6cd672011c755c3cd85c9ffd4e2d10a6f.
Same tests was made with different versions of the Barebox bootloader
and cable detection works flawless.
Please, help to resolve i
26 matches
Mail list logo
