public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: u-boot@lists.denx.de
Subject: [rockchip] broken SPI on RockPro64 and other RK3399 targets
Date: Thu, 5 Nov 2020 22:50:20 +0300	[thread overview]
Message-ID: <dcdf6970-7c91-38fc-7cc7-30e484393af9@gmail.com> (raw)
In-Reply-To: <60671232-d125-e9b0-91bc-e79947ed3b7f@juszkiewicz.com.pl>

On 05/11/2020 20:04, Marcin Juszkiewicz wrote:
> W dniu 05.11.2020 o?17:49, Alper Nebi Yasak pisze:
> 
>> I suspect this change in that commit (rk3399-u-boot.dtsi):
>>
>>>   / {
>>>          aliases {
>>>                  mmc0 = &sdhci;
>>>                  mmc1 = &sdmmc;
>>>                  pci0 = &pcie0;
>>> +               spi1 = &spi1;
>>>          };
>>
>> Can you test adding spi0 = &spi0; above that in the list?
> 
> Helps ;D
> 
> => sf probe
> SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 
> 16 MiB
> 

I looked around a bit more and saw rk3399-<board>-u-boot.dtsi files
(including rockpro64) defining a "spi0 = &spi1;" alias, so I guess what
I suggested would be overridden by that and is actually a no-op?

Maybe two aliases pointing to the same bus is what's really causing the
problem?

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

I guess that's the proper solution if it works.

  reply	other threads:[~2020-11-05 19:50 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 [this message]
2020-11-10 19:45       ` Simon South

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=dcdf6970-7c91-38fc-7cc7-30e484393af9@gmail.com \
    --to=alpernebiyasak@gmail.com \
    --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