All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasco Steinmetz <vasco@kyberraum.net>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org
Subject: Re: Slow performance of Odroid XU4 - cpufreq-dt patch needed?
Date: Thu, 14 Jan 2016 18:30:29 +0100	[thread overview]
Message-ID: <5697DB35.5000601@kyberraum.net> (raw)
In-Reply-To: <CAJKOXPdZr_GhUwtnh1p7wLgzs7DXOQKCVTmmfZJ2LnPao0XJZw@mail.gmail.com>

Hi Krzysztof,

> Where there is no cpufreq driver, everything depends on the
> bootloader. Usually the bootloader sets the initial value of clocks
> and regulators. It shouldn't be the lowest value, though.

Right. The u-bloat in use is the pretty old one provided by hk (modified
u-boot-2012 IIRC), so that may explain unsuitable initial clock values.
Compiled a recent u-boot-2015.10 and also one from trunk, but it's image
size exceeds the hardcoded offsets within the signed firmware bootloader
from hk required to load u-boot.
Had also no success with another hk firmware bootloader I found which
could boot >500K u-boot images. It's a mess on this board (compared to
panda/beagle[bone]s).

Since I haven't got a 1.8v ttl uart cable with that rare connector,
debugging/analyzing bootloader or early kernel issues such as cpu init
or modifying the kconfig is pretty hard.

> There was a patch from Anand Moon ("ARM: dts: use vmmc-supply of
> emmc/sd for exynos5422-odroidxu3") but it did not reach the level of
> acceptance for merging. It would be nice to continue that work.

I saw that and hoped he'd repost an improved version based on your
comments. I'm new to this list so I will not try to bother you by
submitting patches (yet ;-).


Cheers,
Vasco

      reply	other threads:[~2016-01-14 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 16:16 Slow performance of Odroid XU4 - cpufreq-dt patch needed? Vasco Steinmetz
2016-01-13 17:16 ` Ben Gamari
2016-01-14 17:17   ` Vasco Steinmetz
2016-01-14  5:38 ` Krzysztof Kozlowski
2016-01-14 17:30   ` Vasco Steinmetz [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=5697DB35.5000601@kyberraum.net \
    --to=vasco@kyberraum.net \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-samsung-soc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.