Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
Subject: Re: exynos4412: misc issues on Hardkernel Odroid boards
Date: Mon, 09 Feb 2015 09:00:19 +0100	[thread overview]
Message-ID: <54D86913.2050109@samsung.com> (raw)
In-Reply-To: <54D779FB.9070306@math.uni-bielefeld.de>

Hello,

On 2015-02-08 16:00, Tobias Jakobi wrote:
> Hello,
>
> I've collected some of the more serious remaining problems on the
> Hardkernel Odroid boards (here on an X2).
>
> 1) When using cpufreq-exynos and having selected the 'ondemand'
> governor, the system shutdown/reboot process doesn't complete and hangs
> before the end. I'm currently hotfixing this by switching to
> 'performance' governor in a custom initscript.

I didn't observe any issues with 'ondemand' governor. I've just tested it
on next-20150204 with "[PATCH v2 0/3] Add support for hardware reset of eMMC
card on reboot" patches added
(http://www.spinics.net/lists/linux-mmc/msg30621.html) and reboot works 
fine.

> 2) When reading the 'clk_summary' debugfs entry the system locks up
> immediately. Currently hotfixing this by having the ISP powerdomain
> always-on. The problem seems to be known, at least it was mentioned here:
> http://www.spinics.net/lists/linux-samsung-soc/msg39488.html

This is known issue. To properly solve it, we need to rewrite exynos4 clock
driver and integrate power domain support for handling of ISP clocks.
Sylwester can provide more details.

> 3) Maybe related to (1). I'm experiencing high SoC temperatures after
> shutting the system down and leaving the AC connector plugged into the
> board. The shutdown procedure is like mentioned in (1): Switch to
> 'performance' and then do a normal 'shutdown -h now'. I was wondering if
> the Odroid boards need a special shutdown procedure (like designed in
> the odroid-restart handler patch) after all.

Right. That's because CPU is busy looping instead of proper shutdown. 
I've just
posted a patch for solving this issue on all Exynos SoCs, see "[PATCH] 
exynos:
pmu: use PS_HOLD based poweroff for all supported SoCs" thread.

> 4) Spinlock BUGs triggered by the sdhci subsystem (so for the people
> using the system with a SD card). This is also a known problem, I think
> first mentioned here: http://www.spinics.net/lists/linux-mmc/msg27277.html
> Currently fixing this with this patch:
> https://github.com/tobiasjakobi/linux-odroid/commit/abc749843dd7022d01322dca3db0181211a30cd8

The fix for this issue has been queued to mmc-next:
https://git.linaro.org/people/ulf.hansson/mmc.git/commit/017210d1c0dc2e2d3b142985cb31d90b98dc0f0f

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland

  parent reply	other threads:[~2015-02-09  8:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 15:00 exynos4412: misc issues on Hardkernel Odroid boards Tobias Jakobi
2015-02-08  9:52 ` Krzysztof Kozlowski
2015-02-09  8:00 ` Marek Szyprowski [this message]
2015-02-09 20:28   ` Tobias Jakobi
     [not found]     ` <54D9EDC8.6020508@samsung.com>
2015-02-24 13:39       ` Tobias Jakobi
2015-03-03 14:10         ` Marek Szyprowski
2015-04-24 11:24           ` Marek Szyprowski
2015-05-03 12:39             ` Tobias Jakobi
2015-02-14 18:14   ` Tobias Jakobi
2015-02-17 13:24     ` Krzysztof Kozlowski
2015-02-17 13:32       ` Tobias Jakobi
2015-03-20  1:20         ` Tobias Jakobi
2015-03-20  8:25           ` Krzysztof Kozlowski
2015-03-23 16:30             ` Paul Osmialowski

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=54D86913.2050109@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=tjakobi@math.uni-bielefeld.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