From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Sergey Suloev <ssuloev@orpaltech.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: sun6i MIPI DSI driver EoTp
Date: Wed, 13 Mar 2019 16:20:17 +0100 [thread overview]
Message-ID: <20190313152017.zacuzdzdpfbo56a6@flea> (raw)
In-Reply-To: <b6678b38-7236-9f0d-192c-1633908cc43d@orpaltech.com>
[-- Attachment #1.1: Type: text/plain, Size: 1663 bytes --]
On Tue, Mar 12, 2019 at 10:17:49PM +0300, Sergey Suloev wrote:
> On 3/12/19 6:52 PM, Maxime Ripard wrote:
> > 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.
>
> thanks for pointing this
>
> > > 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
>
> does your "should" mean "already supported" or "will be supported" ?
There's code to deal with burst mode but I just realised you wanted
non-burst. This was supported from day one, but we've landed some
quite important fixes that you might want to look at.
> I did a quick compare 4.20.15 with next and there is no difference in MIPI
> DSI driver code (apart from moving phy away).
Which tree have you compared 4.20 with?
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
prev parent reply other threads:[~2019-03-13 15:20 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
2019-03-12 19:17 ` Sergey Suloev
2019-03-13 15:20 ` Maxime Ripard [this message]
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=20190313152017.zacuzdzdpfbo56a6@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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