From: Simon South <simon@simonsouth.net>
To: u-boot@lists.denx.de
Subject: [rockchip] broken SPI on RockPro64 and other RK3399 targets
Date: Tue, 10 Nov 2020 14:45:41 -0500 [thread overview]
Message-ID: <87mtzpj8re.fsf@simonsouth.net> (raw)
In-Reply-To: <dcdf6970-7c91-38fc-7cc7-30e484393af9@gmail.com> (Alper Nebi Yasak's message of "Thu, 5 Nov 2020 22:50:20 +0300")
Alper Nebi Yasak <alpernebiyasak@gmail.com> writes:
> Something else you can test:
> - Remove the aliases block from rk3399-rockpro64-u-boot.dtsi
> - Add "spi[0-5] = &spi[0-5];" aliases to rk3399-u-boot.dtsi
> - Add CONFIG_SF_DEFAULT_BUS=1 to configs/rockpro64-rk3399_defconfig
This fixed for me the same issue on my Pinebook Pro, turning
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
into
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Patch attached, for clarity.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-rockchip-Pinebook-Pro-Fix-SPI-flash.patch
Type: text/x-patch
Size: 1755 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201110/2f61e17d/attachment.bin>
-------------- next part --------------
--
Simon South
simon at simonsouth.net
prev parent reply other threads:[~2020-11-10 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 15:55 [rockchip] broken SPI on RockPro64 and other RK3399 targets Marcin Juszkiewicz
2020-11-05 16:49 ` Alper Nebi Yasak
2020-11-05 17:04 ` Marcin Juszkiewicz
2020-11-05 19:50 ` Alper Nebi Yasak
2020-11-10 19:45 ` Simon South [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtzpj8re.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox