From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932393AbdBHLPc (ORCPT ); Wed, 8 Feb 2017 06:15:32 -0500 Received: from mail-out.m-online.net ([212.18.0.9]:55696 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753861AbdBHLO0 (ORCPT ); Wed, 8 Feb 2017 06:14:26 -0500 X-Auth-Info: unzQu+bzyLz4S1ENn1zKrmldT79qV/TKCY7WoOVO5i8= Subject: Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity To: Daniel Vetter , Stefan Agner References: <20161214204809.27802-1-stefan@agner.ch> Cc: Dave Airlie , Linux Kernel Mailing List , dri-devel From: Marek Vasut Message-ID: <3a550fe7-a111-667a-2433-965d791fa6ab@denx.de> Date: Wed, 8 Feb 2017 11:19:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/08/2017 08:19 AM, Daniel Vetter wrote: > On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: >> On 2016-12-14 13:25, Marek Vasut wrote: >>> On 12/14/2016 09:48 PM, Stefan Agner wrote: >>>> The DRM subsystem specifies the pixel clock polarity from a >>>> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >>>> the controller drives the data on pixel clocks falling edge. >>>> That is the controllers DOTCLK_POL=0 (Default is data launched >>>> at negative edge). >>>> >>>> Also change the data enable logic to be high active by default >>>> and only change if explicitly requested via bus_flags. With >>>> that defaults are: >>>> - Data enable: high active >>>> - Pixel clock polarity: controller drives data on negative edge >>>> >>>> Signed-off-by: Stefan Agner >>> >>> Acked-by: Marek Vasut >>> >> >> This seems not have made into drm-next yet. Not sure what the plan is >> here, who will pick this up? There is also another fix on ML for the >> same driver ("drm: mxsfb: Fix crash when provided invalid DT bindings"). > > By default, driver maintainers are expected to pick up driver patches. > Exception is trivial patches by newcomers, to get them on board fast > (and avoid frustration when a maintainer isn't around). drm-misc and > Dave by default don't pick up anything. Aha, OK. -- Best regards, Marek Vasut