From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Pisati <p.pisati@gmail.com>
Cc: Kevin Hilman <khilman@kernel.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Vivek Gautam <gautamvivek1987@gmail.com>,
Inki Dae <inki.dae@samsung.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Vivek Gautam <gautam.vivek@samsung.com>
Subject: Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init
Date: Fri, 21 Nov 2014 12:33:04 +0100 [thread overview]
Message-ID: <546F22F0.5060204@suse.de> (raw)
In-Reply-To: <20141120234953.GA4010@luxor.wired.org>
Am 21.11.2014 um 00:49 schrieb Paolo Pisati:
> vanilla kgene/for-next as of today:
>
> 7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"
> ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
> 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
> cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
> 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
> 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
> 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
> fc14f9c Linux 3.18-rc5
> ...
>
> plus
>
> 5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 36d908e drm/exynos: dp: Remove support for unused dptx-phy
> 624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices
> 68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel
> support""
>
> vanilla exynos_defconfig with SND_SOC_SNOW disabled.
>
> I should probably try linux-next at this point, but i wonder if people who
> reported kgene/for-next working were testing with a vanilla exynos_defconfig on
> a peach pi.
On Spring, I am able to boot my kgene/for-next based queue with just:
mfd: syscon: Decouple syscon interface from platform devices
arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
with DRM_EXYNOS*=y (except IOMMU) and SND_SOC_SNOW=m enabled in the
config, while using simplefb rather than the Exynos DRM and thus
clk_ignore_unused.
Regarding SND_SOC_SNOW: Note that I recently submitted a patch to enable
module-loading, which is missing in kgene/for-next and -rc5 but is in
linux-next.git - it might uncover problems that previously went
unnoticed: https://patchwork.kernel.org/patch/5235951/
exynos_defconfig has SND_SOC_SNOW=y, whereas multi_v7_defconfig doesn't
have it.
Regards,
Andreas
--
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
next prev parent reply other threads:[~2014-11-21 11:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 13:53 [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init Javier Martinez Canillas
2014-11-18 18:41 ` Kevin Hilman
2014-11-18 20:28 ` Gustavo Padovan
2014-11-18 22:46 ` Kevin Hilman
2014-11-19 10:09 ` Javier Martinez Canillas
2014-11-19 16:52 ` Javier Martinez Canillas
2014-11-19 19:52 ` Kevin Hilman
2014-11-19 22:29 ` Kevin Hilman
2014-11-20 7:06 ` Vivek Gautam
2014-11-20 7:51 ` Vivek Gautam
2014-11-20 8:45 ` Javier Martinez Canillas
2014-11-20 9:52 ` Vivek Gautam
2014-11-20 14:24 ` Pankaj Dubey
2014-11-20 15:57 ` Paolo Pisati
2014-11-20 16:44 ` Javier Martinez Canillas
2014-11-20 16:41 ` Kevin Hilman
2014-11-20 17:47 ` Javier Martinez Canillas
2014-11-20 18:22 ` Kevin Hilman
2014-11-20 23:49 ` Paolo Pisati
2014-11-21 11:33 ` Andreas Färber [this message]
2014-11-21 17:32 ` Ajay kumar
2014-11-21 20:57 ` Javier Martinez Canillas
2014-11-24 10:05 ` Javier Martinez Canillas
2014-11-24 10:36 ` Vivek Gautam
2014-11-24 15:05 ` Andreas Färber
2014-11-25 5:35 ` Ajay kumar
2014-11-20 14:07 ` Inki Dae
2014-11-20 14:28 ` Javier Martinez Canillas
2014-11-20 15:06 ` Inki Dae
2014-11-20 15:26 ` Javier Martinez Canillas
2014-11-20 17:01 ` Inki Dae
2014-11-21 11:19 ` Javier Martinez Canillas
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=546F22F0.5060204@suse.de \
--to=afaerber@suse.de \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gautam.vivek@samsung.com \
--cc=gautamvivek1987@gmail.com \
--cc=inki.dae@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski@samsung.com \
--cc=khilman@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=p.pisati@gmail.com \
/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