On 09/26/2016 02:11 PM, Daniel Vetter wrote:
> On Mon, Sep 26, 2016 at 12:36 PM, Marek Vasut wrote:
>> +
>> +static int mxsfb_atomic_commit(struct drm_device *dev,
>> + struct drm_atomic_state *state, bool
>> nonblock)
>> +{
>> +return drm_ato
On Mon, Sep 26, 2016 at 12:36 PM, Marek Vasut wrote:
> +
> +static int mxsfb_atomic_commit(struct drm_device *dev,
> + struct drm_atomic_state *state, bool nonblock)
> +{
> +return drm_atomic_helper_commit(dev, state, false);
Atomic helpe
On 09/25/2016 10:29 PM, Daniel Vetter wrote:
> On Sun, Sep 25, 2016 at 9:26 PM, Marek Vasut wrote:
>> On 08/28/2016 06:44 PM, Daniel Vetter wrote:
>>> On Fri, Aug 26, 2016 at 04:27:42PM +0200, Marek Vasut wrote:
+static void mxsfb_crtc_mode_set_nofb(struct drm_crtc *crtc)
+{
+st
On Sun, Sep 25, 2016 at 9:26 PM, Marek Vasut wrote:
> On 08/28/2016 06:44 PM, Daniel Vetter wrote:
>> On Fri, Aug 26, 2016 at 04:27:42PM +0200, Marek Vasut wrote:
>>> +static void mxsfb_crtc_mode_set_nofb(struct drm_crtc *crtc)
>>> +{
>>> +struct mxsfb_drm_private *mxsfb = crtc_to_mxsfb_priv(c
On 08/28/2016 06:44 PM, Daniel Vetter wrote:
> On Fri, Aug 26, 2016 at 04:27:42PM +0200, Marek Vasut wrote:
>> Add new driver for the MXSFB controller found in i.MX23/28/6SX .
>> The MXSFB controller is a simple framebuffer controller with one
>> parallel LCD output. Unlike the MXSFB fbdev driver t
On Fri, Aug 26, 2016 at 04:27:42PM +0200, Marek Vasut wrote:
> Add new driver for the MXSFB controller found in i.MX23/28/6SX .
> The MXSFB controller is a simple framebuffer controller with one
> parallel LCD output. Unlike the MXSFB fbdev driver that is used
> on these systems now, this driver us
Add new driver for the MXSFB controller found in i.MX23/28/6SX .
The MXSFB controller is a simple framebuffer controller with one
parallel LCD output. Unlike the MXSFB fbdev driver that is used
on these systems now, this driver uses the DRM/KMS framework.
Signed-off-by: Marek Vasut
Cc: Lucas Stac
