From: "Pavel Machek" <pavel@ucw.cz>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Chris Paterson <chris.paterson2@renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [cip-dev] [PATCH 4.4.y-cip 0/9] Add LCD Panel support for RZ/G1E board
Date: Tue, 28 Jul 2020 22:40:15 +0200 [thread overview]
Message-ID: <20200728204015.GA1012@bug> (raw)
In-Reply-To: <20200728104330.6182-1-biju.das.jz@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
Hi!
> Add LCD Panel support for iWave RZ/G1E board based on r8a7745 SoC.
>
> Backporting the panel patch as it is, requires drm bridge Api changes,
> which is not present at 4.4 kernel. So used the 4.4 rm framework to attach
> the simple panel driver with rgb connector driver. The rgb connector is
> based on the workdone for the lvds connector. The display panel binding
> patch is backported to 4.4 kernel,since the mainline uses yaml file and
> it conflict with corresponding .txt in 4.4 kernel.
>
> Other patches in this series are cherry picked from mainline.
I don't see anything wrong with this, so I'll test/apply it if noone objects.
I guess we could like patches for cip-kernel-config repository to actually enable this in
our testing...
Best regards,
Pavel
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5041): https://lists.cip-project.org/g/cip-dev/message/5041
Mute This Topic: https://lists.cip-project.org/mt/75842037/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-07-28 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 10:43 [cip-dev] [PATCH 4.4.y-cip 0/9] Add LCD Panel support for RZ/G1E board Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 1/9] drm: Add an encoder and connector type enum for DPI Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 2/9] of: add node name compare helper functions Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 3/9] dt-bindings: display: Add bindings for EDT panel Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 4/9] drm/panel: simple: Add EDT panel support Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 5/9] drm: rcar-du: Support panels connected directly to the DPAD outputs Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 6/9] drm: rcar-du: Use the DRM panel API Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 7/9] ARM: shmobile: defconfig: Enable frame buffer console for armadillo800eva Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 8/9] ARM: shmobile: defconfig: Enable support for panels from EDT Biju Das
2020-07-28 10:43 ` [cip-dev] [PATCH 4.4.y-cip 9/9] ARM: dts: iwg22d-sodimm: Enable LCD panel Biju Das
2020-07-28 20:40 ` Pavel Machek [this message]
2020-07-29 6:11 ` [cip-dev] [PATCH 4.4.y-cip 0/9] Add LCD Panel support for RZ/G1E board Nobuhiro Iwamatsu
2020-07-29 6:57 ` Biju Das
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=20200728204015.GA1012@bug \
--to=pavel@ucw.cz \
--cc=biju.das.jz@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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