devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Ulrich Hecht <uli@fpond.eu>,
	linux-mediatek@lists.infradead.org,
	dri-devel@lists.freedesktop.org, jitao.shi@mediatek.com
Cc: mark.rutland@arm.com, stonea168@163.com,
	ajaykumar.rs@samsung.com, architt@codeaurora.org,
	vpalatin@chromium.org, cawa.cheng@mediatek.com,
	yingjoe.chen@mediatek.com, devicetree@vger.kernel.org,
	pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
	robh+dt@kernel.org, seanpaul@chromium.org,
	eddie.huang@mediatek.com, rahul.sharma@samsung.com,
	kernel@pengutronix.de, galak@codeaurora.org,
	enric.balletbo@collabora.com, andy.yan@rock-chips.com
Subject: Re: [PATCH v19 0/2] PS8640 MIPI-to-eDP bridge
Date: Sat, 5 Oct 2019 13:16:56 +0200	[thread overview]
Message-ID: <4df984a5-a917-753e-5870-7453f3d5438e@gmail.com> (raw)
In-Reply-To: <1570216148-22802-1-git-send-email-uli@fpond.eu>

Hi Uli,

On 04/10/2019 21:09, Ulrich Hecht wrote:
> Hi!
> 
> This driver seems to have fallen by the wayside because, while otherwise
> fine, it has a firmware update feature that requires a blob that is not in
> the linux-firmware repo.[1]
> 
> Whatever the cause for that may be, the update code is entirely optional
> (my chip works fine with whatever firmware is currently installed), so I
> have removed it in order to get this merged after all. I have also
> followed various trivial API changes that have piled up since 2016; see
> the individual patches for details.
> 
> I'm using this driver on an Acer Chromebook R13 ("Elm"); see
> https://github.com/uli/kernel/tree/elm-working-5.4.
> 

Thanks for your effort to get things upstream.
I just tried your branch on my R13. I had to do a trivial config change I had to
do, as I don't have and care about the bluetooth FW right now.
But after that my screen keeps black. I was able to build and boot
elm-working-5.3 and elm-working-5.2.

Unfortunatley I don't have a serial console on the Chromebook, so it's difficult
to find out where it hangs. Can you please double check if your new
elm-working-5.4 actually really works?

Thanks,
Matthias

> CU
> Uli
> 
> [1] https://patchwork.kernel.org/patch/9427543/
> 
> Jitao Shi (2):
>   Documentation: bridge: Add documentation for ps8640 DT properties
>   drm/bridge: Add I2C based driver for ps8640 bridge
> 
>  .../devicetree/bindings/display/bridge/ps8640.txt  |  44 ++
>  drivers/gpu/drm/bridge/Kconfig                     |  12 +
>  drivers/gpu/drm/bridge/Makefile                    |   1 +
>  drivers/gpu/drm/bridge/parade-ps8640.c             | 672 +++++++++++++++++++++
>  4 files changed, 729 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/display/bridge/ps8640.txt
>  create mode 100644 drivers/gpu/drm/bridge/parade-ps8640.c
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-10-05 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 19:09 [PATCH v19 0/2] PS8640 MIPI-to-eDP bridge Ulrich Hecht
     [not found] ` <1570216148-22802-1-git-send-email-uli-qwV78thtvt0@public.gmane.org>
2019-10-04 19:09   ` [PATCH v19 1/2] Documentation: bridge: Add documentation for ps8640 DT properties Ulrich Hecht
2019-10-04 19:09   ` [PATCH v19 2/2] drm/bridge: Add I2C based driver for ps8640 bridge Ulrich Hecht
2019-10-05 11:16 ` Matthias Brugger [this message]
     [not found]   ` <4df984a5-a917-753e-5870-7453f3d5438e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-10-06 12:32     ` [PATCH v19 0/2] PS8640 MIPI-to-eDP bridge Ulrich Hecht

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=4df984a5-a917-753e-5870-7453f3d5438e@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=ajaykumar.rs@samsung.com \
    --cc=andy.yan@rock-chips.com \
    --cc=architt@codeaurora.org \
    --cc=cawa.cheng@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eddie.huang@mediatek.com \
    --cc=enric.balletbo@collabora.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jitao.shi@mediatek.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=rahul.sharma@samsung.com \
    --cc=robh+dt@kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=stonea168@163.com \
    --cc=uli@fpond.eu \
    --cc=vpalatin@chromium.org \
    --cc=yingjoe.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).