devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Artem Lapkin <email2tema@gmail.com>,
	robh+dt@kernel.org
Cc: khilman@baylibre.com, jbrunet@baylibre.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	art@khadas.com, nick@khadas.com, gouwa@khadas.com
Subject: Re: [PATCH 4/8] arm64: dts: meson: remove fixed memory size for Khadas VIM3/VIM3L meson-khadas-vim3
Date: Fri, 25 Sep 2020 09:40:28 +0200	[thread overview]
Message-ID: <3aa15c85-5dec-52df-c97f-67d45572d5be@baylibre.com> (raw)
In-Reply-To: <CAFBinCBtGqDgPH0VhW2awPzYSVFN++HNCA5=L6VVMRW64=AY9A@mail.gmail.com>

On 25/09/2020 09:37, Martin Blumenstingl wrote:
> Hi Artem,
> 
> On Fri, Sep 25, 2020 at 5:31 AM Artem Lapkin <email2tema@gmail.com> wrote:
>>
>> no need force setup memory size!
>> VIM3 boards have 2Gb and 4Gb variants
>> memory size will be automatically defined
>>
>> mainline uboot works properly in any case
>> but old vendor uboot works not properly for 4Gb variants
> can you be more specific with what "does not work properly"? is Linux
> then only able to use 2GB or is there any other problem?
> 
> overall this sounds like a bug in the vendor u-boot to me
> I don't see that we have any other Amlogic .dts which needs this hack,
> so I'd like to hear the feedback from the device-tree maintainers (for
> example Rob) as well

AFAIK the vendor u-boot updates the memory correctly, what it doesn't is adding
the reserved memory zones.

Neil

> 
> 
> Best regards,
> Martin
> 


  reply	other threads:[~2020-09-25  7:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  3:30 [PATCH 0/8] dts updates and fixes for Khadas VIM1 VIM2 VIM3 VIML boards Artem Lapkin
2020-09-25  3:30 ` [PATCH 1/8] arm64: dts: meson: update spifc node on Khadas VIM2 meson-gxm-khadas-vim2 Artem Lapkin
2020-09-25  7:41   ` Neil Armstrong
2020-09-25  7:51   ` Martin Blumenstingl
2020-09-28  7:54     ` Neil Armstrong
2020-09-25  3:30 ` [PATCH 2/8] arm64: dts: meson: update leds node on Khadas VIM3/VIM3L boards meson-khadas-vim3 Artem Lapkin
2020-09-25  7:36   ` Neil Armstrong
2020-09-25  3:30 ` [PATCH 3/8] arm64: dts: meson: update leds node on Khadas VIM3/VIM3L board meson-khadas-vim3 Artem Lapkin
2020-09-25  7:39   ` Neil Armstrong
2020-09-25  3:30 ` [PATCH 4/8] arm64: dts: meson: remove fixed memory size for Khadas VIM3/VIM3L meson-khadas-vim3 Artem Lapkin
2020-09-25  7:37   ` Martin Blumenstingl
2020-09-25  7:40     ` Neil Armstrong [this message]
2020-09-25  3:30 ` [PATCH 5/8] arm64: dts: meson: remove reset-gpios from ethernet node for VIM2 meson-gxm-khadas-vim2 Artem Lapkin
2020-09-25  7:41   ` Martin Blumenstingl
     [not found]     ` <CAKaHn9+CWLJYN1Tt46VxBGNBEbVVJZWeL6ZJSf9w-5DmoxrvgQ@mail.gmail.com>
2020-09-25  8:04       ` Martin Blumenstingl
     [not found]         ` <CAKaHn9K6O8u6Br84S63V0PDFBhiRbMdd4-bvC5FxFe6izj_Dvg@mail.gmail.com>
2020-09-25 11:26           ` Martin Blumenstingl
     [not found]             ` <CAKaHn9JxKBKW5AYvUNBAA+sNcHfNQNrx95NtLMnrfd0ypOaAoA@mail.gmail.com>
2020-09-28 20:41               ` Martin Blumenstingl
2020-09-25  3:30 ` [PATCH 6/8] arm64: dts: meson: disable vrtc for VIM3L boards meson-khadas-vim3 Artem Lapkin
2020-09-25  7:44   ` Neil Armstrong
2020-09-25  3:30 ` [PATCH 7/8] arm64: dts: meson: enable RTC for VIM1 meson-gxl-s905x-khadas-vim Artem Lapkin
2020-09-25  7:31   ` Martin Blumenstingl
2020-09-25  3:30 ` [PATCH 8/8] arm64: dts: meson: enable RTC for VIM2 meson-gxm-khadas-vim2 Artem Lapkin
2020-09-25  8:58   ` Jerome Brunet

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=3aa15c85-5dec-52df-c97f-67d45572d5be@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=art@khadas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=email2tema@gmail.com \
    --cc=gouwa@khadas.com \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=nick@khadas.com \
    --cc=robh+dt@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).