From: Inki Dae <inki.dae@samsung.com>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, cw00.choi@samsung.com,
devicetree@vger.kernel.org, Donghwa Lee <dh09.lee@samsung.com>,
linux-kernel@vger.kernel.org, krzk@kernel.org,
jh80.chung@samsung.com, kgene@kernel.org,
dri-devel@lists.freedesktop.org,
Hyungwon Hwang <human.hwang@samsung.com>,
Hoegeun Kwon <hoegeun.kwon@samsung.com>
Subject: Re: [PATCH v7 3/4] drm/panel: Add support for S6E3HA2 panel driver on TM2 board
Date: Fri, 06 Jan 2017 17:36:56 +0900 [thread overview]
Message-ID: <586F5728.1010800@samsung.com> (raw)
In-Reply-To: <20170106081806.h4y7o57kjbibau6l@gangnam.samsung>
2017년 01월 06일 17:18에 Andi Shyti 이(가) 쓴 글:
> Hi Inki,
>
> Thanks for the reply, but...
>
>>>> +static const struct drm_display_mode default_mode = {
>>>> + .clock = 222372,
>>>> + .hdisplay = 1440,
>>>> + .hsync_start = 1440 + 1,
>>>> + .hsync_end = 1440 + 1 + 1,
>>>> + .htotal = 1440 + 1 + 1 + 1,
>>>> + .vdisplay = 2560,
>>>> + .vsync_start = 2560 + 1,
>>>> + .vsync_end = 2560 + 1 + 1,
>>>> + .vtotal = 2560 + 1 + 1 + 15,
>>>> + .vrefresh = 60,
>>>> + .flags = 0,
>>>> +};
>>>
>>> how is this working with tm2e? Are these values valid for both
>>> the boards?
>>
>> We don't need to consider tm2e board with two reasones,
>> 1. there is no tm2e board support in mainline
>> 2. the panel on tm2 would be a little bit different from one on tm2e
>
> ... this display in the Tizen Kernel is supported by both:
> tm2 [1] and tm2e [2]. The only differences are:
Why tm2e dts file is in mainline? Seems communication miss with Chanwoo. :(
>
> TM2:
> clock-frequency = <14874444>;
> hactive = <1440>;
>
> TM2E:
> clock-frequency = <16523724>;
> hactive = <1600>;
>
> I don't know much about the differences you mention in point 2,
> but it's a pity to drop support only because we don't want to put
> in the dts the 'hactive', and 'clock-frequency' properties.
Anyway, tm2e board is already in mainline so Panel driver may need to identify what kinds of panel is probed to decide porch values. I think there are relevant registers in MCU of the Panel device to check version or similar thing.
Thanks.
>
> Andi
>
> [1] https://git.tizen.org/cgit/platform/kernel/linux-exynos/tree/arch/arm64/boot/dts/exynos/exynos5433-tm2.dts?h=tizen#n1284
> [2] https://git.tizen.org/cgit/platform/kernel/linux-exynos/tree/arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts?h=tizen#n1270
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-06 8:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170105102011epcas1p416e0495978dbce7e73e900eb69a4b7ad@epcas1p4.samsung.com>
2017-01-05 10:20 ` [PATCH v7 0/4] Add support for the S6E3HA2 panel on TM2 board Hoegeun Kwon
[not found] ` <CGME20170105102012epcas5p3666c67cfc82d2439c993f917f8e2d0ce@epcas5p3.samsung.com>
2017-01-05 10:20 ` [PATCH v7 1/4] drm/exynos: mic: Add mode_set callback function Hoegeun Kwon
[not found] ` <1483611609-23522-2-git-send-email-hoegeun.kwon-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-01-11 5:33 ` Inki Dae
[not found] ` <CGME20170105102012epcas5p308c2d3ed269d9bf76f76f1d38422eb54@epcas5p3.samsung.com>
[not found] ` <1483611609-23522-1-git-send-email-hoegeun.kwon-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-01-05 10:20 ` [PATCH v7 2/4] drm/exynos: mic: Fix parse_dt function Hoegeun Kwon
2017-01-05 12:16 ` Andrzej Hajda
2017-01-11 5:33 ` Inki Dae
[not found] ` <CGME20170105102012epcas1p4ddeb577ea84b5c2cdf7029666b2091c1@epcas1p4.samsung.com>
2017-01-05 10:20 ` [PATCH v7 3/4] drm/panel: Add support for S6E3HA2 panel driver on TM2 board Hoegeun Kwon
2017-01-05 18:09 ` Krzysztof Kozlowski
[not found] ` <1483611609-23522-4-git-send-email-hoegeun.kwon-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-01-06 5:22 ` Andi Shyti
2017-01-06 5:32 ` Inki Dae
[not found] ` <586F2BF3.8080400-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-01-06 8:18 ` Andi Shyti
2017-01-06 8:36 ` Inki Dae [this message]
[not found] ` <586F5728.1010800-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-01-09 7:37 ` Andrzej Hajda
2017-01-09 9:19 ` Inki Dae
2017-01-09 9:53 ` Andrzej Hajda
2017-01-10 1:15 ` Inki Dae
[not found] ` <CGME20170105102013epcas5p3098ddb99e516ef138cc41d63c7591a79@epcas5p3.samsung.com>
2017-01-05 10:20 ` [PATCH v7 4/4] arm64: dts: exynos: Add support for S6E3HA2 panel device " Hoegeun Kwon
[not found] ` <1483611609-23522-5-git-send-email-hoegeun.kwon-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-01-06 4:49 ` Andi Shyti
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=586F5728.1010800@samsung.com \
--to=inki.dae@samsung.com \
--cc=andi.shyti@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dh09.lee@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegeun.kwon@samsung.com \
--cc=human.hwang@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).