All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar, Shobhit" <shobhit.kumar@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
	Shobhit Kumar <shobhit.kumar@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>, jacob.jun.pan@intel.com
Subject: Re: [RFC v2 3/4] drm/panel: Add new panel driver based on crystal cove pmic
Date: Mon, 12 Jan 2015 14:32:37 +0530	[thread overview]
Message-ID: <54B38DAD.30606@linux.intel.com> (raw)
In-Reply-To: <54B3854A.1020309@linux.intel.com>

On 1/12/2015 1:56 PM, Kumar, Shobhit wrote:
> On 1/9/2015 6:38 PM, Jani Nikula wrote:
>> On Fri, 02 Jan 2015, Shobhit Kumar <shobhit.kumar@intel.com> wrote:
>>> This driver provides support for the "crystal_cove_panel" cell device.
>>> On BYT-T pmic has to be used to enable/disable panel.
>>
>> This needs to be sent to dri-devel.
>
> Will do for the updated patch after addressing all your comments.

Also do we really need to make it as part of drm. How about keeping this 
internal to i915 as most likely no one else other than i915 will use it ?

>
>>
>> With the comments below addressed, and with the disclaimer that I have
>> no idea about the pmic registers or required sleeps, this is
>>
>> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>>
>>>
>>> Signed-off-by: Shobhit Kumar <shobhit.kumar@intel.com>
>>> ---

>>> +module_platform_driver(crystalcove_panel_driver);
>>> +
>>> +MODULE_AUTHOR("Shobhit Kumar <shobhit.kumar@linux.intel.com");
>>> +MODULE_DESCRIPTION("Intel Crystal Cove Panel Driver");
>>> +MODULE_LICENSE("GPL v2");
>>
>> This conflicts with the copyright header of the file.

I have seen drivers in kernel header both with Copyright and GPL V2. 
Example - "drivers/gpu/drm/panel/panel-s6e8aa0.c"

I can change to  MODULE_LICENSE("GPL and additional rights");

Regards
Shobhit
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-01-12  9:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 13:41 [RFC v2 0/4] Crystal Cove PMIC based Panel and Backlight Control Shobhit Kumar
2015-01-02 13:41 ` [RFC v2 1/4] drm: Add support to find drm_panel by name Shobhit Kumar
2015-01-09 12:50   ` Jani Nikula
2015-01-12  7:37     ` Kumar, Shobhit
2015-01-12 23:08     ` [Intel-gfx] " Daniel Vetter
2015-01-13 15:14       ` Andrzej Hajda
2015-01-16 12:19       ` Thierry Reding
2015-01-02 13:41 ` [RFC v2 2/4] mfd: Add a new cell device for panel controlled by crystal cove pmic Shobhit Kumar
2015-01-02 13:41 ` [RFC v2 3/4] drm/panel: Add new panel driver based on " Shobhit Kumar
2015-01-09 13:08   ` Jani Nikula
2015-01-12  8:26     ` Kumar, Shobhit
2015-01-12  9:02       ` Kumar, Shobhit [this message]
2015-01-02 13:41 ` [RFC v2 4/4] drm/i915: Enable DSI panel enable/disable based on PMIC Shobhit Kumar
2015-01-09 13:17   ` Jani Nikula
2015-01-12  8:23     ` Kumar, Shobhit
2015-01-12 23:11       ` Daniel Vetter
2015-01-07  5:06 ` [RFC v2 0/4] Crystal Cove PMIC based Panel and Backlight Control Kumar, Shobhit
2015-01-09 13:20 ` Jani Nikula

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=54B38DAD.30606@linux.intel.com \
    --to=shobhit.kumar@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jacob.jun.pan@intel.com \
    --cc=jani.nikula@intel.com \
    --cc=shobhit.kumar@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 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.