From: Brian Starkey <Brian.Starkey@arm.com>
To: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Mihail Atanassov <Mihail.Atanassov@arm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Maxime Ripard <mripard@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
nd <nd@arm.com>, Sean Paul <sean@poorly.run>
Subject: Re: [RFC,3/3] drm/komeda: Allow non-component drm_bridge only endpoints
Date: Fri, 18 Oct 2019 09:12:15 +0000 [thread overview]
Message-ID: <20191018091213.k6bka3tajy2vez6l@DESKTOP-E1NTVVP.localdomain> (raw)
In-Reply-To: <20191018065657.GA19117@jamwan02-TSP300>
On Fri, Oct 18, 2019 at 06:57:05AM +0000, james qian wang (Arm Technology China) wrote:
>
> Hi Brian:
>
> Can this convince you to fully swap to bridge ?
Not until those patches materialise and land, no :-)
>
> Actually even there is no fix, we won't real encounter such rmmod problem,
> since we always build the bridge/tda998 (by Y) into the image.
>
If you say so. I think the folks here like having drm as a module to
make it easy to patch things without a reboot.
-Brian
> Thanks
> James
> > --
> > RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> > FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
> > According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-10-18 9:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 14:34 [PATCH 0/3] drm/komeda: Support for drm_bridge endpoints Mihail Atanassov
2019-10-04 14:34 ` [PATCH 1/3] drm/komeda: Consolidate struct komeda_drv allocations Mihail Atanassov
2019-10-04 14:34 ` [PATCH 2/3] drm/komeda: Memory manage struct komeda_drv in probe/remove Mihail Atanassov
2019-10-04 14:34 ` [RFC PATCH 3/3] drm/komeda: Allow non-component drm_bridge only endpoints Mihail Atanassov
2019-10-09 5:54 ` [RFC,3/3] " james qian wang (Arm Technology China)
2019-10-16 15:51 ` Mihail Atanassov
2019-10-16 16:22 ` Brian Starkey
2019-10-17 3:07 ` james qian wang (Arm Technology China)
2019-10-17 8:20 ` Brian Starkey
2019-10-17 10:21 ` james qian wang (Arm Technology China)
2019-10-17 10:48 ` Brian Starkey
2019-10-17 11:41 ` Russell King - ARM Linux admin
2019-10-18 6:57 ` james qian wang (Arm Technology China)
2019-10-18 9:12 ` Brian Starkey [this message]
2019-10-22 8:42 ` Daniel Vetter
2019-10-22 8:48 ` Russell King - ARM Linux admin
2019-10-22 8:50 ` Daniel Vetter
2019-10-22 14:42 ` Russell King - ARM Linux admin
2019-10-22 14:53 ` Russell King - ARM Linux admin
2019-10-24 8:03 ` Mihail Atanassov
2019-10-24 5:21 ` james qian wang (Arm Technology China)
2019-10-18 6:38 ` james qian wang (Arm Technology China)
2019-10-18 11:01 ` Mihail Atanassov
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=20191018091213.k6bka3tajy2vez6l@DESKTOP-E1NTVVP.localdomain \
--to=brian.starkey@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Mihail.Atanassov@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=sean@poorly.run \
/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).