From: Manuel Traut <manut@mecka.net>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: "Ondřej Jirman" <megi@xff.cz>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jessica Zhang" <quic_jesszhan@quicinc.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Sandy Huang" <hjc@rock-chips.com>,
"Mark Yao" <markyao0591@gmail.com>,
"Diederik de Haas" <didi.debian@cknow.org>,
Segfault <awarnecke002@hotmail.com>,
"Arnaud Ferraris" <aferraris@debian.org>,
Danct12 <danct12@riseup.net>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v3 4/4] arm64: dts: rockchip: Add devicetree for Pine64 PineTab2
Date: Sat, 27 Jan 2024 10:31:08 +0100 [thread overview]
Message-ID: <ZbTNXL6s_wQugVC5@mecka.net> (raw)
In-Reply-To: <6efe305c-4ab4-43c1-ab6d-64bdf1d81a2f@kwiboo.se>
Hi Jonas,
On Wed, Jan 03, 2024 at 03:19:25PM +0100, Jonas Karlman wrote:
> Hi Manuel,
>
> On 2024-01-03 14:40, Manuel Traut wrote:
> > Hi Jonas and Ondřej,
> >
> >>>> +&sfc {
> >>>> + pinctrl-names = "default";
> >>>> + pinctrl-0 = <&fspi_dual_io_pins>;
> >>>> + status = "okay";
> >>>> + #address-cells = <1>;
> >>>> + #size-cells = <0>;
> >>>> +
> >>>> + flash@0 {
> >>>> + compatible = "jedec,spi-nor";
> >>>> + reg = <0>;
> >>>> + spi-max-frequency = <24000000>;
> >>>
> >>> That's a bit on the low side. The flash chip should work for all commands up to
> >>> 80MHz https://megous.com/dl/tmp/b428ad9b85ac4633.png and SGM3157YC6 switch
> >>> for the FSPI-CLK should have high enough bandwidth, too.
> >>
> >> I agree that this is a little bit on the low side, it was a safe rate
> >> that I used for U-Boot. U-Boot required an exact rate of the supported
> >> sfc clk rates: 24, 50, 75, 100, 125 or 150 MHz.
> >>
> >> Please also note that the SPI NOR flash chip used in PineTab2 is not a
> >> GigaDevice GD25LQ128E, it should be a SiliconKaiser SK25LP128, same as
> >> found in the Pine64 PinePhone Pro.
> >
> > The schematics for v2.0 reference a GD25LQ128EWIGR. I never checked the jedec
> > id. How did you retrieve this information, or is it maybe a difference in v0.1
> > and 2.0?
>
> This was when working on mainline U-Boot for the PineTab2 (and other
> rk356x devices). See [1] for a pending U-Boot patch that is waiting on a
> proper mainline linux devicetree for the PT2.
>
> The JEDEC ID is reported as 0x257018 on my v2.0 production unit, and
> does not match the JEDEC ID for GD25LQ128E (0xc86018) referenced in
> the schematics.
>
> I found that the JEDEC ID 0x257018 was referenced in prior patches
> related to the SK25LP128 SPI NOR flash chip used in Pine64 PinePhone Pro.
>
> I have only ever tested the 24 MHz rate, but I am expecting that e.g.
> 100 MHz also should work. Will not be able to test on my PT2 until at
> earliest next week.
>
> [1] https://github.com/Kwiboo/u-boot-rockchip/commit/66562d6eaf2c11a9f97fcdba379d3ceda8aa70ef
I found the time to verify that 100 MHz is also working.
Will include this in v4
Thanks for your help
Manuel
next prev parent reply other threads:[~2024-01-27 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 16:15 [PATCH v3 0/4] arm64: rockchip: Pine64 PineTab2 support Manuel Traut
2024-01-02 16:15 ` [PATCH v3 1/4] dt-bindings: display: panel: Add BOE TH101MB31IG002-28A panel Manuel Traut
2024-01-02 16:15 ` [PATCH v3 2/4] drm/panel: Add driver for " Manuel Traut
2024-01-08 18:24 ` Jessica Zhang
2024-01-02 16:15 ` [PATCH v3 3/4] dt-bindings: arm64: rockchip: Add Pine64 PineTab2 Manuel Traut
2024-01-02 16:15 ` [PATCH v3 4/4] arm64: dts: rockchip: Add devicetree for " Manuel Traut
2024-01-02 18:07 ` Ondřej Jirman
2024-01-02 20:56 ` Jonas Karlman
2024-01-02 21:18 ` Ondřej Jirman
2024-01-03 13:40 ` Manuel Traut
2024-01-03 14:19 ` Jonas Karlman
2024-01-05 16:46 ` Manuel Traut
2024-01-27 9:31 ` Manuel Traut [this message]
2024-01-03 4:09 ` Dang Huynh
2024-01-03 13:22 ` Manuel Traut
2024-01-03 9:42 ` Ondřej Jirman
2024-01-05 16:11 ` Manuel Traut
2024-01-05 16:48 ` Ondřej Jirman
2024-01-26 20:30 ` Manuel Traut
2024-01-12 9:25 ` (subset) [PATCH v3 0/4] arm64: rockchip: Pine64 PineTab2 support neil.armstrong
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=ZbTNXL6s_wQugVC5@mecka.net \
--to=manut@mecka.net \
--cc=aferraris@debian.org \
--cc=airlied@gmail.com \
--cc=awarnecke002@hotmail.com \
--cc=conor+dt@kernel.org \
--cc=danct12@riseup.net \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=markyao0591@gmail.com \
--cc=megi@xff.cz \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.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