From: Daniel Stone <daniel@fooishbar.org>
To: Rob Clark <robdclark@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Sean Paul <seanpaul@google.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
jg1.han@samsung.com,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"moderated list:ARM/S5P EXYNOS AR..."
<linux-samsung-soc@vger.kernel.org>,
Ajay kumar <ajaynumb@gmail.com>,
Pannaga Bhushan Reddy Patel <bhushan.r@samsung.com>,
Prashanth G <prashanth.g@samsung.com>,
Ajay Kumar <ajaykumar.rs@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 03/14] drm/bridge: make bridge registration independent of drm flow
Date: Fri, 30 Jan 2015 16:08:04 +0000 [thread overview]
Message-ID: <CAPj87rMXRGB48k_jnfuxNUh4W6JP63vb4Ak1bkFoNj8wSmq+Tw@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGs8GbgYMLmaPjGnXAv=Gsf6gMhNj+Zt0-2GKHOnHv4d4Q@mail.gmail.com>
Hi,
On 30 January 2015 at 15:37, Rob Clark <robdclark@gmail.com> wrote:
> ok, so I probably should have had a closer look at this before it
> landed in drm-next, so if it is too late to revert (and deal w/
> untangling subsequent patches that depend on this) some of these
> issues we'll just have to fix with follow-on patches.
>
> 1) needs headerdoc for new fxns in drm_bridge.c, and needs to be added
> in drm.tmpl
> 2) as far as I can tell, the new approach to cleaning up bridge
> objects is to just let them leak !?!
>
> I'll also need to update the new bridge in the msm edp code..
> although that isn't such a big deal if I knew how this was *supposed*
> to work.. since what is there now at least doesn't look right..
Given how long these patches sat around doing being passively NACKed
by discussions going around in circles, and how useful they are, I'd
be much more in favour of fixing them up than reverting and going
through the whole circus again ...
Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: daniel@fooishbar.org (Daniel Stone)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/14] drm/bridge: make bridge registration independent of drm flow
Date: Fri, 30 Jan 2015 16:08:04 +0000 [thread overview]
Message-ID: <CAPj87rMXRGB48k_jnfuxNUh4W6JP63vb4Ak1bkFoNj8wSmq+Tw@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGs8GbgYMLmaPjGnXAv=Gsf6gMhNj+Zt0-2GKHOnHv4d4Q@mail.gmail.com>
Hi,
On 30 January 2015 at 15:37, Rob Clark <robdclark@gmail.com> wrote:
> ok, so I probably should have had a closer look at this before it
> landed in drm-next, so if it is too late to revert (and deal w/
> untangling subsequent patches that depend on this) some of these
> issues we'll just have to fix with follow-on patches.
>
> 1) needs headerdoc for new fxns in drm_bridge.c, and needs to be added
> in drm.tmpl
> 2) as far as I can tell, the new approach to cleaning up bridge
> objects is to just let them leak !?!
>
> I'll also need to update the new bridge in the msm edp code..
> although that isn't such a big deal if I knew how this was *supposed*
> to work.. since what is there now at least doesn't look right..
Given how long these patches sat around doing being passively NACKed
by discussions going around in circles, and how useful they are, I'd
be much more in favour of fixing them up than reverting and going
through the whole circus again ...
Cheers,
Daniel
next prev parent reply other threads:[~2015-01-30 16:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 16:38 [PATCH V9 00/14] drm/exynos: few patches to enhance bridge chip support Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 01/14] drm/bridge: ptn3460: Few trivial cleanups Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 02/14] drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 04/14] drm/bridge: ptn3460: Convert to i2c driver model Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-29 14:29 ` Gustavo Padovan
2015-01-29 14:29 ` Gustavo Padovan
2015-01-29 14:39 ` Ajay kumar
2015-01-29 14:39 ` Ajay kumar
2015-01-20 16:38 ` [PATCH V9 06/14] drm/bridge: ptn3460: support drm_panel Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 07/14] drm/bridge: ptn3460: probe connector at the end of bridge attach Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 08/14] drm/bridge: ptn3460: use gpiod interface Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 09/14] Documentation: drm: bridge: move to video/bridge Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 10/14] Documentation: devicetree: Add vendor prefix for parade Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-02-04 15:12 ` Rob Herring
2015-02-04 15:12 ` Rob Herring
2015-01-20 16:38 ` [PATCH V9 12/14] drm/bridge: Add i2c based driver for ps8622/ps8625 bridge Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-29 14:42 ` Ajay kumar
2015-01-29 14:42 ` Ajay kumar
[not found] ` <CAEC9eQMv_qbQJ=DKz=KznxkGbE2O08DUTwSDtpcfZeHtesEewA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-30 11:43 ` Thierry Reding
2015-01-30 11:43 ` Thierry Reding
2015-01-20 16:38 ` [PATCH V9 13/14] ARM: dts: snow: represent the connection between bridge and panel using videoport and endpoints Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
[not found] ` <1421771935-31618-14-git-send-email-ajaykumar.rs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-23 7:01 ` Kukjin Kim
2015-01-23 7:01 ` Kukjin Kim
2015-01-27 4:27 ` Ajay kumar
2015-01-27 4:27 ` Ajay kumar
2015-02-04 15:30 ` Kukjin Kim
2015-02-04 15:30 ` Kukjin Kim
[not found] ` <1421771935-31618-1-git-send-email-ajaykumar.rs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-20 16:38 ` [PATCH 03/14] drm/bridge: make bridge registration independent of drm flow Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-30 15:37 ` Rob Clark
2015-01-30 15:37 ` Rob Clark
[not found] ` <CAF6AEGs8GbgYMLmaPjGnXAv=Gsf6gMhNj+Zt0-2GKHOnHv4d4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-30 15:59 ` Russell King - ARM Linux
2015-01-30 15:59 ` Russell King - ARM Linux
2015-02-02 9:16 ` Ajay kumar
2015-02-02 9:16 ` Ajay kumar
2015-01-30 16:08 ` Daniel Stone [this message]
2015-01-30 16:08 ` Daniel Stone
2015-02-02 9:14 ` Ajay kumar
2015-02-02 9:14 ` Ajay kumar
2015-02-03 12:03 ` Thierry Reding
2015-02-03 12:03 ` Thierry Reding
2015-01-20 16:38 ` [PATCH V9 05/14] drm/exynos: dp: support drm_bridge Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 11/14] Documentation: bridge: Add documentation for ps8622 DT properties Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
2015-01-20 16:38 ` [PATCH V9 14/14] ARM: dts: peach-pit: represent the connection between bridge and panel using videoport and endpoints Ajay Kumar
2015-01-20 16:38 ` Ajay Kumar
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=CAPj87rMXRGB48k_jnfuxNUh4W6JP63vb4Ak1bkFoNj8wSmq+Tw@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=ajaykumar.rs@samsung.com \
--cc=ajaynumb@gmail.com \
--cc=bhushan.r@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jg1.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prashanth.g@samsung.com \
--cc=robdclark@gmail.com \
--cc=seanpaul@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.