From: Eric Anholt <eric@anholt.net>
To: Linus Walleij <linus.walleij@linaro.org>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/tve200: Replace custom connector with panel bridge
Date: Fri, 01 Sep 2017 11:42:11 -0700 [thread overview]
Message-ID: <87bmmul0qk.fsf@anholt.net> (raw)
In-Reply-To: <20170831213514.29267-1-linus.walleij@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]
Linus Walleij <linus.walleij@linaro.org> writes:
> This replaces the custom connector in the TVE200 with the
> panel bridge helper. As long as we're just using panels
> and no other bridges, this works just fine.
Yeah, we definitely need a way to get the bus_flags/bus_formats from the
next link in the bridge chain in general, rather than needing to reach
into the panel's connector (or being just out of luck in a 2-bridge
chain). That seems like it'll be straightforward to do later, and this
is a good start.
I don't think you need the new #includes in tve200_drm.h, but other than
maybe that change:
Reviewed-by: Eric Anholt <eric@anholt.net>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-09-01 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 21:35 [PATCH] drm/tve200: Replace custom connector with panel bridge Linus Walleij
2017-09-01 18:42 ` Eric Anholt [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=87bmmul0qk.fsf@anholt.net \
--to=eric@anholt.net \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=seanpaul@chromium.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