From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Sergey Suloev <ssuloev@orpaltech.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: sun6i MIPI DSI driver EoTp
Date: Tue, 12 Mar 2019 16:52:53 +0100 [thread overview]
Message-ID: <20190312155253.kdsqgby32jgagdta@flea> (raw)
In-Reply-To: <ff953218-219e-7f92-476d-91e2b9904776@orpaltech.com>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
Hi,
On Mon, Mar 11, 2019 at 09:43:36PM +0300, Sergey Suloev wrote:
> according to MIPI DSI spec chapter 8.8.2 the EoTp packet can be enabled or
> disabled on the protocol level.
> It seems like that it might be required for the panel I am working on (Himax
> HX8379A-based panel).
> Here is some crappy driver I found on github showing that it might be an
> issue [1]
>
> May I ask you if this feature supported by sun6i MIPI DSI driver and
> where ?
> As there is no datasheet available, could you please help to support this
> feature (if not yet) ?
I haven't seen any panel that used it so far, so I have no idea.
I guess this would be controlled through
SUN6I_DSI_BASIC_CTL0_HS_EOTP_EN in the driver.
> The second point is that the panel requires NON-BURST-WITH-SYNC-EVENTS mode.
> Could it be a problem with the current driver?
That should be supported in -next
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-12 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 18:43 sun6i MIPI DSI driver EoTp Sergey Suloev
2019-03-12 15:52 ` Maxime Ripard [this message]
2019-03-12 19:17 ` Sergey Suloev
2019-03-13 15:20 ` Maxime Ripard
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=20190312155253.kdsqgby32jgagdta@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssuloev@orpaltech.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