From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org,
shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v3 0/3] Rockchip: generalize GRF setup
Date: Fri, 06 Jan 2017 22:46:45 +0100 [thread overview]
Message-ID: <4525397.n2uf8fF4JB@phil> (raw)
In-Reply-To: <20161116230304.8432-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Am Donnerstag, 17. November 2016, 00:03:01 CET schrieb Heiko Stuebner:
> The General register files contain a big bunch of settings for various
> components. Things like the automatic sdmmc/jtag switch may even affect
> us in a bad way, while that property (and possibly others) are not even
> part of the dw_mmc controller itself.
>
> And while the rk3288 could still carry adaptions to these defaults
> in its mach files, this is no longer possible on the arm64 socs, while
> things like the jtag-switch from above still can affect us there.
applied these 3 to my drivers branch for 4.11
prev parent reply other threads:[~2017-01-06 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 23:03 [PATCH v3 0/3] Rockchip: generalize GRF setup Heiko Stuebner
[not found] ` <20161116230304.8432-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2016-11-16 23:03 ` [PATCH v3 1/3] dt-bindings: add used but undocumented rockchip grf compatible values Heiko Stuebner
2016-11-16 23:03 ` [PATCH v3 2/3] soc: rockchip: add driver handling grf setup Heiko Stuebner
2016-11-16 23:03 ` [PATCH v3 3/3] ARM: rockchip: drop rk3288 jtag/mmc switch handling Heiko Stuebner
2017-01-06 21:46 ` Heiko Stuebner [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=4525397.n2uf8fF4JB@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.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