From: b.zolnierkie@samsung•com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4/4] ARM64: dts: exynos5433: add jpeg node
Date: Mon, 28 Sep 2015 13:54:37 +0200 [thread overview]
Message-ID: <2466182.YdnXZtSWXI@amdc1976> (raw)
In-Reply-To: <5608FFBD.1030306@samsung.com>
Hi,
On Monday, September 28, 2015 05:52:13 PM Krzysztof Kozlowski wrote:
> W dniu 21.09.2015 o 18:59, Andrzej Pietrasiewicz pisze:
> > Hi Hans,
> >
> > W dniu 21.09.2015 o 11:50, Hans Verkuil pisze:
> >> On 18-09-15 16:21, Andrzej Pietrasiewicz wrote:
> >>> From: Marek Szyprowski <m.szyprowski@samsung•com>
> >>>
> >>> Add Exynos 5433 jpeg h/w codec node.
> >>>
> >>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung•com>
> >>> Signed-off-by: Andrzej Pietrasiewicz <andrzej.p@samsung•com>
> >>> ---
> >>> arch/arm64/boot/dts/exynos/exynos5433.dtsi | 21 +++++++++++++++++++++
> >>> 1 file changed, 21 insertions(+)
> >>>
> >>> diff --git a/arch/arm64/boot/dts/exynos/exynos5433.dtsi
> >>> b/arch/arm64/boot/dts/exynos/exynos5433.dtsi
> >>
> >> This dtsi file doesn't exist in the media-git tree. What is the story
> >> here?
> >>
> >> Should this go through a different subsystem?
> >>
> >> I think the media subsystem can take patches 1-3 and whoever does DT
> >> patches can
> >> take this patch, right?
> >>
> >
> > The cover letter explains that the series is rebased onto Mauro's
> > master with Kukjin's branch merged. The latter does contain
> > the exynos5433.dtsi. That said, yes, taking patches 1-3 in
> > media subsystem and leaving DT patch to someone else is the
> > way to go.
>
> Although Kukjin picked Exynos 5433 ARM64 patches but they were not
> accepted upstream by arm-soc. He rolled it for few releases but:
> 1. Reason for not accepting by arm-soc was not resolved - there is no DTS.
> 2. Kukjin did not rebase the branch for 4.4... which maybe means that he
> wants to drop it?
> 3. Anyone (but me...) can send Galaxy Note4 (Exynos5433) DTS file based
> on sources on opensource.samsung.com. The DTS there is for 32-bit but it
> can be probably easily adjusted for ARM64.
>
> All of this means that Device Tree support for this driver can't be
> merged now and effort for mainlining 5433 may be unfortunately wasted...
Exynos5433 support is being incrementally merged (clocks, drm, phy,
pinctrl, thermal and tty support is already in upstream or -next).
I don't know why DTS changes got stuck in Kukjin's tree (Kukjin,
could you please explain?) but I think that this shouldn't not stop
us from continuing Exynos5433 upstreaming effort.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2015-09-28 11:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 14:20 [PATCH 0/4] Exynos 5433 jpeg h/w codec support Andrzej Pietrasiewicz
2015-09-18 14:20 ` [PATCH 1/4] s5p-jpeg: generalize clocks handling Andrzej Pietrasiewicz
2015-09-18 14:29 ` Jacek Anaszewski
2015-09-18 14:20 ` [PATCH 2/4] s5p-jpeg: add support for 5433 Andrzej Pietrasiewicz
2015-09-18 14:30 ` Jacek Anaszewski
2015-09-18 14:20 ` [PATCH 3/4] MAINTAINERS: add exynos jpeg codec maintainers Andrzej Pietrasiewicz
2015-09-18 14:30 ` Jacek Anaszewski
2015-09-18 14:21 ` [PATCH 4/4] ARM64: dts: exynos5433: add jpeg node Andrzej Pietrasiewicz
2015-09-21 9:50 ` Hans Verkuil
2015-09-21 9:59 ` Andrzej Pietrasiewicz
2015-09-21 11:41 ` Mauro Carvalho Chehab
2015-09-21 12:28 ` Sylwester Nawrocki
2015-09-21 12:55 ` Andrzej Pietrasiewicz
2015-09-28 8:52 ` Krzysztof Kozlowski
2015-09-28 11:54 ` Bartlomiej Zolnierkiewicz [this message]
2015-09-28 12:02 ` Krzysztof Kozlowski
2015-09-30 6:35 ` Kukjin Kim
2015-09-30 6:46 ` Chanwoo Choi
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=2466182.YdnXZtSWXI@amdc1976 \
--to=b.zolnierkie@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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