in, because the DM virtual root driver isn't
initialized yet in...
drivers/timer/timer-class.c:dm_timer_init()
[WORKAROUND]
Move error handling to (next patch in this serie)...
lib/time.c
Signed-off-by: Johannes Krottmayer
Cc: Wolfgang Denk
Cc: Thomas Chou
Cc: Rick Chen
Cc: Leo
Cc: Bin Meng
Cc
to the timer_early_get_count() and
timer_early_get_rate().
Signed-off-by: Johannes Krottmayer
Cc: Wolfgang Denk
Cc: Thomas Chou
Cc: Rick Chen
Cc: Leo
Cc: Bin Meng
Cc: Sean Anderson
Cc: Anup Patel
Cc: Thomas Chou
---
lib/time.c | 42 +-
1 file changed, 33
/timer/riscv_timer.c
I don't know who maintains these base libraries and base
functions, so I used the copyright holders. For the driver
I added the required maintainers to CC.
Signed-off-by: Johannes Krottmayer
Cc: Wolfgang Denk
Cc: Thomas Chou
Cc: Rick Chen
Cc: Leo
Cc: Bin Meng
Cc: Sean
Description:
When CONFIG_TIMER_EARLY is selected only the timer_early_* functions
will be called. With this patch first gd->timer will be checked, if the
DM timer is available, it uses the DM timer. When gd->timer is empty,
the timer_early_* functions will be called.
Signed-off-by: Jo
Description:
When CONFIG_TIMER_EARLY is selected and the timer driver implements
timer_early_get_count() and timer_early_get_rate() this leads to
an EAGAIN error in initf_dm() one some configurations.
Signed-off-by: Johannes Krottmayer
Cc: Tom Rini
---
common/board_f.c | 6 --
1 file
regards,
Johannes
Signed-off-by: Johannes Krottmayer
Cc: Tom Rini
---
Johannes Krottmayer (2):
common: board_f.c: Fix EAGAIN issue when CONFIG_TIMER_EARLY is
selected
lib: time.c: Try also DM timer, when CONFIG_TIMER_EARLY is selected
common/board_f.c | 6 --
lib/time.c
Fix documentation path in deprecated warning message about device
driver.
Signed-off-by: Johannes Krottmayer
---
tools/buildman/test.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/buildman/test.py b/tools/buildman/test.py
index 714bb3e4f9..27287438ee 100644
Fix documentation path in warning message about deprecated device driver.
Signed-off-by: Johannes Krottmayer
---
Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index e6fc80aa6f..0af5065624 100644
--- a/Makefile
+++ b/Makefile
@@ -1080,7
Fix doc path in warning messages.
Okay?
Johannes Krottmayer (2):
Makefile: Fix doc path in warning message
tools: buildman: Fix doc path in warning message
Makefile | 4 ++--
tools/buildman/test.py | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.34.1
rkspi driver;
>>
>> - rk3328-u-boot.dtsi
>>
>> BTW: the patch no need reply-to previous mail, you can make a new thread.
>>
>> Thanks,
>>
>> - Kever
>>
>> On 2020/7/4 上午2:08, Johannes Krottmayer wrote:
>>> Add U-Boot SPI suppo
Add U-Boot SPI Flash support for the PINE64 Rock64 board
Signed-off-by: Johannes Krottmayer
Cc: Matwey V. Kornilov
---
configs/rock64-rk3328_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configs/rock64-rk3328_defconfig b/configs/rock64-rk3328_defconfig
index f123826358
Add U-Boot SPI Flash support for the PINE64 Rock64 board
Signed-off-by: Johannes Krottmayer
Cc: Matwey V. Kornilov
---
arch/arm/dts/rk3328-rock64-u-boot.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/rk3328-rock64-u-boot.dtsi
b/arch/arm/dts/rk3328-rock64-u
This patch series adds SPI Flash support for the PINE64 Rock64
board.
Tested with the version 2.0 of the board.
Johannes Krottmayer (2):
ARM: dts: rk3328-rock64: Add SPI Flash support
configs: rock64-rk3328_defconfig: Add SPI Flash support
arch/arm/dts/rk3328-rock64-u-boot.dtsi | 6
Add SPI support for the RK3328 clock driver
Signed-off-by: Johannes Krottmayer
Cc: Kever Yang
Cc: Jagan Teki
---
drivers/clk/rockchip/clk_rk3328.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/clk/rockchip/clk_rk3328.c
b/drivers/clk/rockchip
Add U-Boot SPI support for the RK3328
Signed-off-by: Johannes Krottmayer
Cc: Kever Yang
Cc: Jagan Teki
---
arch/arm/dts/rk3328-u-boot.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/dts/rk3328-u-boot.dtsi b/arch/arm/dts/rk3328-u-boot.dtsi
index c69e13e11e..c980daae99
This patch series adds support for the RK3328 SPI
controller.
Johannes Krottmayer (3):
drivers: clk: rockchip: clk_rk3328: Add SPI support
drivers: spi: rk_spi: Add support for RK3328
ARM: dts: rk3328: Add SPI support
arch/arm/dts/rk3328-u-boot.dtsi | 5 +
drivers/clk/rockchip
Add support for the RK3328 SPI controller
Signed-off-by: Johannes Krottmayer
Cc: Kever Yang
Cc: Jagan Teki
---
I don't know if "rk3399_spi_params" is also required for the
RK3328 SPI controller.
Probing, Reading, Writing and Erasing of a flash device works
with the SF comma
Hi Yakov,
have you fixed the issue?
I'm not a real developer from the U-Boot project, but I had a similar
issue on a PINE64 Rock64 board. The error code -19 was a missing alias
in the Device-Tree files on my used board.
Fixed this issue with the correct alias. Maybe it's the same issue
on your
Add SPI Flash support for the PINE64 Rock64 board
Signed-off-by: Johannes Krottmayer
Cc: Kever Yang
Cc: Jagan Teki
---
Initial SPI Flash support.
Okay?
arch/arm/dts/rk3328-rock64-u-boot.dtsi | 6 ++
configs/rock64-rk3328_defconfig| 2 ++
2 files changed, 8 insertions(+)
diff
Add U-Boot SPI support for the RK3328
Signed-off-by: Johannes Krottmayer
Cc: Kever Yang
Cc: Jagan Teki
---
It's a initial SPI support. Not sure if "rk3399_spi_params" is also
needed. Probing of the SPI flash devices works. Tested with the
PINE64 Rock64 board.
Okay?
arch/arm/dt
17:52, Johannes Krottmayer wrote:
> Sorry for my late response.
>
> Thanks for the suggestions.
>
> On 22.05.20 at 16:28, Peter Robinson wrote:
>> Make sure you enable the driver for the actual flash chip too, some of
>> the popular ones are:
>> CONFIG_SPI_FLASH_W
Sorry for my late response.
Thanks for the suggestions.
On 22.05.20 at 16:28, Peter Robinson wrote:
> Make sure you enable the driver for the actual flash chip too, some of
> the popular ones are:
> CONFIG_SPI_FLASH_WINBOND=y
> CONFIG_SPI_FLASH_MACRONIX=y
> CONFIG_SPI_FLASH_SPANSION=y
>
Hi,
I have a special question about reserved memory regions one some
architectures. For the first time only for ARM and ARM64.
Is there a equivalent or similar mechanism in U-Boot to tell the
Kernel, which memory regions are free available for the Kernel? On
x86 with GRUB as boot loader, I can
Add a short description in the ZYNQ documentation how to prepare a SD card and
copy the related images to SD card.
Signed-off-by: Johannes Krottmayer
Cc: Michal Simek
---
Changes for v2
- added missing partition number in mount command
I think, it's necessary for the documentation to avoid
On 03.06.20 at 08:23, Michal Simek wrote:
> On 02. 06. 20 17:55, Johannes Krottmayer wrote:
>> Add a short description in the ZYNQ documentation how to prepare a SD card
>> and
>> copy the related images to SD card.
>>
>> I think, it's necessary for the
Add a short description in the ZYNQ documentation how to prepare a SD card and
copy the related images to SD card.
I think, it's necessary for the documentation to avoid such user questions
(like mine) in this list.
Okay?
Signed-off-by: Johannes Krottmayer
---
doc/board/xilinx/zynq.rst | 19
On 01.06.20 at 10:18, Michal Simek wrote:
> SPL is community effort and not supported flow by Xilinx. If you want to
> use it, use it but don't expect any help from Xilinx to help you with
> issues. I take care about it, use it but there is no planning behind. I
> am fixing issues for me and for
Okay, thanks for the fast reply!
At the time I wrote this mail, I didn't read the docs.
Off-topic:
Are there plans for U-Boot to create a default image (including
FSBL, bitstream and U-Boot)?
For example (additional build step):
$ export BITSTREAM=/path/to/fpga.bit
For now I use Vivado to
Hello,
I just noticed that the support for the board Zybo-Z7
in mainline U-Boot is no longer available.
Are there some reasons why it was dropped? Couldn't
find any information in the list archive.
Thanks in advance!
--
Best regards,
Johannes K.
c
>
> to check what's wrong.
>
>
> Thanks,
>
> - Kever
>
> On 2020/5/20 上午7:41, Johannes Krottmayer wrote:
>> Hello,
>>
>> I just compiled U-Boot v2020.04 for a PINE64 Rock media board.
>> It compiles fine without errors, but when I try to probe the
Hello,
I just compiled U-Boot v2020.04 for a PINE64 Rock media board.
It compiles fine without errors, but when I try to probe the
on board flash I get an error:
=> sf probe
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)
=>
SPI is activated in the Device-Tree blob. I
31 matches
Mail list logo
