Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp535686imm; Wed, 26 Sep 2018 02:54:44 -0700 (PDT) X-Google-Smtp-Source: ACcGV62mP4o0BSOZgVPE00/rzEQlJkFd3oVO1J1HCka01E3syKG7m5T+gA4EZ42CswnECu95qnl4 X-Received: by 2002:a17:902:7244:: with SMTP id c4-v6mr5207702pll.339.1537955684031; Wed, 26 Sep 2018 02:54:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537955684; cv=none; d=google.com; s=arc-20160816; b=AGCpsw3stunR1CAUn6Q9hQtwOjFQSSbMTiVgfxgjrZl3jiWgjVYgZuv7yn1ZdD5Fuf Pd78JPGEAF3eQV0iXYhDtKFIiTsbq+5zPcf1CDQoHAQStTRL8oQP40Q2fP4Sq15GqKu3 /78/MEQ2oHZ7W81k/GxURi0nlu85AlAB0OiHMpNuLjiOcYaHehDjDPeUgRUBSZEIT03+ eyVbqd7YSZ3GnlhTEC5X4VWa1zadYQzNI2x4QCg2aLau7ximmfcFUGZ+wQcKLtJXyXjJ xAZUkYlc2u6EfEnnKr0Al6yKT00VhdgIKgep+MCbgYMGvmH1W9f2PELNcjzYPCHGfxgE pVsw== 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:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=IkyPiQ3BniH5uw+8lEGFV6H/fGaNr2TNma/YCPNyUtY=; b=QE+py4sXHsDMCmtE8W+r+uz4TpI10W4BCHjHBHKOF2frteGShedTIdDcGfSpBs/Bdk fNbxzgIOYIxJnSDKYnpKr0YeYz2xPfAQoIEPmblqeilJjrzHhi5V0JgT41nF2EQOGAm4 0NdkHjMMZU6kSCP79UuMmATjg4XcFsF08B4+C8nO6b7P2Kx0I+zTgsFXeqrkA/1GO5YK /5YjIZFPvS61z2tQm5574USxbWvaDpeI7q/tmH+8twWLTY5gUMoYj7rXOoicmnsqMyo4 +w3rE0kCXLB987WUsc9ZE3PRBjH3StzBPjsBq1v+dIm+ekUKafnl2aqa0+4bk01m+jBE q0zg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w18-v6si4955287ply.66.2018.09.26.02.54.28; Wed, 26 Sep 2018 02:54:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727504AbeIZQGF (ORCPT + 99 others); Wed, 26 Sep 2018 12:06:05 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:12711 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726565AbeIZQGF (ORCPT ); Wed, 26 Sep 2018 12:06:05 -0400 Received: from DGGEMS414-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id D456C99D3827A; Wed, 26 Sep 2018 17:53:53 +0800 (CST) Received: from [127.0.0.1] (10.202.226.41) by DGGEMS414-HUB.china.huawei.com (10.3.19.214) with Microsoft SMTP Server id 14.3.399.0; Wed, 26 Sep 2018 17:53:46 +0800 Subject: Re: [PATCH 0/3] HiBMC driver fixes To: Xinliang Liu References: <1537550727-21257-1-git-send-email-john.garry@huawei.com> CC: "Liuxinliang (Matthew Liu)" , XinWei Kong , Feng Chen , "David Airlie" , Daniel Vetter , , Linux Kernel Mailing List , dri-devel , Linuxarm , Rongrong Zou From: John Garry Message-ID: <77674be9-734f-12e3-5327-dee89f1f0299@huawei.com> Date: Wed, 26 Sep 2018 10:53:38 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.226.41] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26/09/2018 10:41, Xinliang Liu wrote: > On Wed, 26 Sep 2018 at 16:46, John Garry wrote: >> >> On 26/09/2018 04:00, Xinliang Liu wrote: >>> Thanks John, good addressing! >>> The root cause as you said, our hibmc previous frame buffer format >>> depth setting is wrong which does not pass the new format sanity >>> checking drm_mode_legacy_fb_format. >>> For this series, Reviewed-by: Xinliang Liu >>> Applied to hisilicon-drm-next. >> >> I can't see this branch in the git associated with this driver from its >> MAINTAINERS entry (git://github.com/xin3liang/linux.git), but please > Not a branch, it is a tag: drm-hisilicon-next-2018-09-26 > >> ensure these fixes are included in 4.19 > > As it doesn't affect 4.19-rcx, I send a PULL for 4.20. > See mail "[GIT PULL] drm-hisilicon-next-2018-09-26" When Chris' change goes into 4.20 - which I suspect will be before yours - boot-time bisect will be broken. John > >> >> Thanks, >> John >> >>> >>> Thanks, >>> Xinliang >>> >>> On Sun, 23 Sep 2018 at 20:32, John Garry wrote: >>>> >>>> This patchset fixes a couple of issues in probing the HiBMC driver, as >>>> follows: >>>> - fix the probe error path to not carry an error code in the pointer >>>> - don't use invalid legacy fb bpp/depth combination >>>> >>>> Another more trivial patch is for using the standard Huawei PCI vendor ID >>>> instead of hard-coding it. >>>> >>>> Tested on Huawei D05 board. I can see tux on BMC VGA console. >>>> >>>> John Garry (3): >>>> drm/hisilicon: hibmc: Do not carry error code in HiBMC framebuffer >>>> pointer >>>> drm/hisilicon: hibmc: Don't overwrite fb helper surface depth >>>> drm/hisilicon: hibmc: Use HUAWEI PCI vendor ID macro >>>> >>>> drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 2 +- >>>> drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_fbdev.c | 2 +- >>>> 2 files changed, 2 insertions(+), 2 deletions(-) >>>> >>>> -- >>>> 1.9.1 >>>> >>>> _______________________________________________ >>>> dri-devel mailing list >>>> dri-devel@lists.freedesktop.org >>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel >>> >>> . >>> >> >> > > . >