Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3626011ybt; Tue, 30 Jun 2020 07:34:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzSIPtVusH/IMdDV4Mej2YQRA/0Tn0sBPBo2orjO5BpCbjzmADxIB5KvnTaxn3aC8nPOeiu X-Received: by 2002:a17:906:95d6:: with SMTP id n22mr18546210ejy.138.1593527686950; Tue, 30 Jun 2020 07:34:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593527686; cv=none; d=google.com; s=arc-20160816; b=ujR+OSrsdiKYp4e3u9w54Vqa7ZJ9WLMZJ1MieBnAVSDIlE4MCqQMNQsWPz1L+N9xvR zFy+bP+1KXc+wm1wtsndqbTGDy5BIDQIb6WQVF2L93cuoZrgBzMd+eNmLdeUvLIPGf6R EcGPq9+5kbwezRCe5unsfPOLYrudj/CZQHjLvHiXpc42uAtJ/m2gvmMJXa8L1MMicqdF J3OQWNqjQnNdWPTkuNiIJumV4MnNNVNXJMXYXlO/jgPRAVXEOB2+anflWwMok8r4EHuc Q5BkWUVpQxi/8Otrye3sO7qWcYbqmsCeCOYiZLbGwIzmh5+om4rNC5x877iQziHRD/7c FhQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=q2vwe4tdsc7FRE9DTX47nxZiB6yPqqm40cjM/c9Ktos=; b=rpzndKxilHSBMGFQM0JcjDBXwwLBklfsT+F4vDOvfT14Vcoo1gSpd5GN4KJou/wlNK zhSnKc37VmuA3nqcnatA2oOsGiKf6WLaVTJrJciVHO3nHAOfBm6ISvpUimAfh4ixSeal qf1AkkpMBFDp9F9Ddtr14BOdzsNdysP9mrbtVyeJHw8jsa3X/ofUUevUcawN/xbbBSZO y1v9PCpPgFUzyRHyqCt5WJPqoSxZOUR+nyMtj7FuBZaTCCTL+oiml/BZ47Nr9jzJc3/q QfCxik97gkioyGEhUGu4NdjXJuJg6RD5FxKiX/UKNbZ5nu78DeNOi1oKCyLnzJHsbCwg Yd4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j8si1753959edt.383.2020.06.30.07.34.24; Tue, 30 Jun 2020 07:34:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388890AbgF3OeD (ORCPT + 99 others); Tue, 30 Jun 2020 10:34:03 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:34220 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726576AbgF3OeC (ORCPT ); Tue, 30 Jun 2020 10:34:02 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: eballetbo) with ESMTPSA id 7ACC42A4ED6 Subject: Re: [RESEND PATCH v4 0/7] Convert mtk-dsi to drm_bridge API and get EDID for ps8640 bridge To: Sam Ravnborg Cc: linux-kernel@vger.kernel.org, Collabora Kernel ML , Chun-Kuang Hu , Jernej Skrabec , drinkcat@chromium.org, Jonas Karlman , David Airlie , Thomas Zimmermann , dri-devel@lists.freedesktop.org, Neil Armstrong , Andrzej Hajda , linux-mediatek@lists.infradead.org, Laurent Pinchart , hsinyi@chromium.org, matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org References: <20200615203108.786083-1-enric.balletbo@collabora.com> <20200620213302.GC74146@ravnborg.org> From: Enric Balletbo i Serra Message-ID: <593a4666-d6aa-7d16-f3a0-ba3713047d84@collabora.com> Date: Tue, 30 Jun 2020 16:33:56 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <20200620213302.GC74146@ravnborg.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sam, Chun-Kuan, On 20/6/20 23:33, Sam Ravnborg wrote: > Hi Enric > > On Mon, Jun 15, 2020 at 10:31:01PM +0200, Enric Balletbo i Serra wrote: >> (This resend is to fix some trivial conflicts due the merge window) >> >> The PS8640 dsi-to-eDP bridge driver is using the panel bridge API, >> however, not all the components in the chain have been ported to the >> drm_bridge API. Actually, when a panel is attached the default panel's mode >> is used, but in some cases we can't get display up if mode getting from >> eDP control EDID is not chosen. >> >> This series address that problem, first implements the .get_edid() >> callback in the PS8640 driver (which is not used until the conversion is >> done) and then, converts the Mediatek DSI driver to use the drm_bridge >> API. >> >> As far as I know, we're the only users of the mediatek dsi driver in >> mainline, so should be safe to switch to the new chain of drm_bridge API >> unconditionally. >> >> The patches has been tested on a Acer Chromebook R13 (Elm) running a >> Chrome OS userspace and checking that the valid EDID mode reported by >> the bridge is selected. >> >> Changes in v4: >> - Remove double call to drm_encoder_init(). (Chun-Kuang Hu) >> - Cleanup the encoder in mtk_dsi_unbind(). (Chun-Kuang Hu) >> >> Changes in v3: >> - Replace s/bridge/next bridge/ for comment. (Laurent Pinchart) >> - Add the bridge.type. (Laurent Pinchart) >> - Use next_bridge field to store the panel bridge. (Laurent Pinchart) >> - Add the bridge.type field. (Laurent Pinchart) >> - This patch requires https://lkml.org/lkml/2020/4/16/2080 to work >> properly. >> - Move the bridge.type line to the patch that adds drm_bridge support. (Laurent Pinchart) >> >> Changes in v2: >> - Do not set connector_type for panel here. (Sam Ravnborg) >> >> Enric Balletbo i Serra (7): >> drm/bridge: ps8640: Get the EDID from eDP control >> drm/bridge_connector: Set default status connected for eDP connectors >> drm/mediatek: mtk_dsi: Rename bridge to next_bridge >> drm/mediatek: mtk_dsi: Convert to bridge driver >> drm/mediatek: mtk_dsi: Use simple encoder >> drm/mediatek: mtk_dsi: Use the drm_panel_bridge API >> drm/mediatek: mtk_dsi: Create connector for bridges > > Patch seems ready to apply. Will they be applied to a mediatek tree > or to drm-misc-next? > Or shall we take the first two patches via drm-misc-next, and the > remaning via a mediatek tree? (I hope not) > I think the only concern is from Chun-Kuan regarding patch 7/7 "drm/mediatek: mtk_dsi: Create connector for bridges" whether we should support the old API or not, but the discussion stalled. Thanks, Enric > Sam > > >> >> drivers/gpu/drm/bridge/parade-ps8640.c | 12 ++ >> drivers/gpu/drm/drm_bridge_connector.c | 1 + >> drivers/gpu/drm/mediatek/mtk_dsi.c | 269 ++++++++----------------- >> 3 files changed, 97 insertions(+), 185 deletions(-) >> >> -- >> 2.27.0 >> >> _______________________________________________ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/dri-devel >