From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] drm/tilcdc: Some fixes for LCDC rev1
Date: Wed, 31 Aug 2016 15:11:40 -0700 [thread overview]
Message-ID: <m28tvck2qr.fsf@baylibre.com> (raw)
In-Reply-To: <e659bff8-7c8e-35ed-e834-1e00d5c32931@ti.com> (Jyri Sarha's message of "Tue, 23 Aug 2016 19:24:42 +0300")
Hi Jyri,
Jyri Sarha <jsarha@ti.com> writes:
> On 08/23/16 15:56, Karl Beldan wrote:
>> Hi,
>>
>> I found some missing bits for rev1 of the LCDC and here are some of the
>> changes I am using to use the DRM driver on an LCDCK (which has a rev1).
>> 1/3 seems required by rev1 of the IP and without it my the LCDC on my
>> LCDK keeps can't sync, 2/3 is required by the driver logic, while 3/3
>> is less of a requirement.
>
> I'll drop 3/3, because my recent patches should take care of that:
> http://www.spinics.net/lists/devicetree/msg138885.html
>
> However, there will be v2 round of those patches. Only the DT binding
> and its default value should change.
>
>> Although 1,2/3 would have fitted drm-fixes I based them on drm-next as
>> 2/3 would conflict with the recent changes in drm-next.
>>
>
> I'll pick these two up for my next pull request. Thanks!
>
Can you share a branch which has your current series and these fixes
included, so we can use that as a baseline for further development?
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: Karl Beldan <karl.beldan+oss@gmail.com>,
Sekhar Nori <nsekhar@ti.com>,
dri-devel@lists.freedesktop.org,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Karl Beldan <kbeldan@baylibre.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] drm/tilcdc: Some fixes for LCDC rev1
Date: Wed, 31 Aug 2016 15:11:40 -0700 [thread overview]
Message-ID: <m28tvck2qr.fsf@baylibre.com> (raw)
In-Reply-To: <e659bff8-7c8e-35ed-e834-1e00d5c32931@ti.com> (Jyri Sarha's message of "Tue, 23 Aug 2016 19:24:42 +0300")
Hi Jyri,
Jyri Sarha <jsarha@ti.com> writes:
> On 08/23/16 15:56, Karl Beldan wrote:
>> Hi,
>>
>> I found some missing bits for rev1 of the LCDC and here are some of the
>> changes I am using to use the DRM driver on an LCDCK (which has a rev1).
>> 1/3 seems required by rev1 of the IP and without it my the LCDC on my
>> LCDK keeps can't sync, 2/3 is required by the driver logic, while 3/3
>> is less of a requirement.
>
> I'll drop 3/3, because my recent patches should take care of that:
> http://www.spinics.net/lists/devicetree/msg138885.html
>
> However, there will be v2 round of those patches. Only the DT binding
> and its default value should change.
>
>> Although 1,2/3 would have fitted drm-fixes I based them on drm-next as
>> 2/3 would conflict with the recent changes in drm-next.
>>
>
> I'll pick these two up for my next pull request. Thanks!
>
Can you share a branch which has your current series and these fixes
included, so we can use that as a baseline for further development?
Thanks,
Kevin
next prev parent reply other threads:[~2016-08-31 22:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:56 [PATCH 0/3] drm/tilcdc: Some fixes for LCDC rev1 Karl Beldan
2016-08-23 12:56 ` Karl Beldan
2016-08-23 12:56 ` [PATCH 1/3] drm/tilcdc: Adjust the FB_CEILING address Karl Beldan
2016-08-23 12:56 ` Karl Beldan
2016-08-23 12:57 ` [PATCH 2/3] drm/tilcdc: Enable EOF interrupts for v1 LCDC Karl Beldan
2016-08-23 12:57 ` Karl Beldan
2016-08-23 12:57 ` [PATCH 3/3] drm/tilcdc: Advertise the DRM_FORMATs according to the IP revision Karl Beldan
2016-08-23 12:57 ` Karl Beldan
2016-08-23 16:24 ` [PATCH 0/3] drm/tilcdc: Some fixes for LCDC rev1 Jyri Sarha
2016-08-23 16:24 ` Jyri Sarha
2016-08-26 16:54 ` Karl Beldan
2016-08-26 16:54 ` Karl Beldan
2016-08-31 22:11 ` Kevin Hilman [this message]
2016-08-31 22:11 ` Kevin Hilman
2016-09-02 12:29 ` Jyri Sarha
2016-09-02 12:29 ` Jyri Sarha
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=m28tvck2qr.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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 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.