From: Shobhit Kumar <shobhit.kumar@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: vijayakumar.balakrishnan@intel.com,
intel-gfx <intel-gfx@lists.freedesktop.org>,
yogesh.mohan.marimuthu@intel.com
Subject: Re: [PATCH 1/4] drm/i915: Add more dev ops for MIPI sub encoder
Date: Thu, 24 Oct 2013 17:43:05 +0530 [thread overview]
Message-ID: <52690ED1.40301@intel.com> (raw)
In-Reply-To: <87mwlz6pq0.fsf@intel.com>
On 10/24/2013 01:54 PM, Jani Nikula wrote:
> On Thu, 24 Oct 2013, Shobhit Kumar <shobhit.kumar@intel.com> wrote:
>> On 10/23/2013 07:52 PM, Jani Nikula wrote:
>>> So I think let's keep trying to find the right abstractions to separate
>>> the DSI core and the panel drivers, make it possible to support several
>>> panels with one driver, and make it possible to have independent drivers
>>> for panels that don't fit the assumptions of the generic panel driver.
>>>
>>> Does that conflict with your goals? Are we in agreement here?
>>
>> Definetely we are in agreement and perfectly aligns with my goals.
>
> That's relieving, I'm happy we're on the same page now. :)
Me too :)
>
>> But is it okay to work towards pushing sub-encoder based design for
>> immidiate short term and then work to convert on drm_bridge because I
>> can see that drm_bridge callbacks will need additions defintely and it
>> might take some time to get that done. In the meantime can we push
>> current driver with already suggested changes to get atleast a working
>> base ?
>
> I'm okay with this. Daniel is pushing for drm_bridge, and I'm also
> optimistic about that, but perhaps we have to see what we really need
> first. The current sub-encoder model is more flexible for that in the
> short term.
>
> However I, and others, will need to know where we are heading, so please
> do pay attention to splitting up the patches and explaining why they are
> needed. Sometimes it's helpful to provide draft/RFC patches on top just
> for that.
I will push updated smaller patches with clear reasoning for them.
>
> Finally, I am glad you're contributing directly to upstream now. It
> makes a huge difference in the long run.
>
Yeah, I wanted to do earlier but sometimes its all matter of bandwidth
and priorities. Hopefully I will be able to continue to do so, now that
I have started.
Thanks for all your inputs.
Regards
Shobhit
next prev parent reply other threads:[~2013-10-24 12:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 12:21 [PATCH 0/4] drm/i915: Baytrail MIPI DSI support Updated Shobhit Kumar
2013-10-21 12:21 ` [PATCH 1/4] drm/i915: Add more dev ops for MIPI sub encoder Shobhit Kumar
2013-10-21 13:27 ` Jani Nikula
2013-10-22 9:39 ` Shobhit Kumar
2013-10-22 11:53 ` Jani Nikula
2013-10-23 12:52 ` Shobhit Kumar
2013-10-23 14:22 ` Jani Nikula
2013-10-24 8:01 ` Shobhit Kumar
2013-10-24 8:24 ` Jani Nikula
2013-10-24 12:13 ` Shobhit Kumar [this message]
2013-10-21 12:21 ` [PATCH 2/4] drm/i915: Use FLISDSI interface for band gap reset Shobhit Kumar
2013-10-21 13:30 ` Jani Nikula
2013-10-21 12:21 ` [PATCH 3/4] drm/i915: Compute dsi_clk from pixel clock Shobhit Kumar
2013-10-21 13:28 ` Ville Syrjälä
2013-10-22 9:15 ` Shobhit Kumar
2013-10-21 13:44 ` Jani Nikula
2013-10-22 9:25 ` Shobhit Kumar
2013-10-21 12:21 ` [PATCH 4/4] drm/i915: Parameterize the MIPI enabling sequnece and adjust the sequence Shobhit Kumar
2013-10-21 13:23 ` Ville Syrjälä
2013-10-22 9:06 ` Shobhit Kumar
2013-10-22 10:49 ` Ville Syrjälä
2013-10-23 12:57 ` Shobhit 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=52690ED1.40301@intel.com \
--to=shobhit.kumar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=vijayakumar.balakrishnan@intel.com \
--cc=yogesh.mohan.marimuthu@intel.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