From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1FA32FC616B for ; Fri, 13 Sep 2024 17:48:00 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 2A0A610ED5E; Fri, 13 Sep 2024 17:47:59 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (1024-bit key; unprotected) header.d=chromium.org header.i=@chromium.org header.b="Z4X/RjV1"; dkim-atps=neutral Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com [209.85.214.179]) by gabe.freedesktop.org (Postfix) with ESMTPS id 7A22C10ED61 for ; Fri, 13 Sep 2024 17:47:58 +0000 (UTC) Received: by mail-pl1-f179.google.com with SMTP id d9443c01a7336-206aee4073cso26628345ad.1 for ; Fri, 13 Sep 2024 10:47:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1726249678; x=1726854478; darn=lists.freedesktop.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=8IH/fKZ7WlUWd6MAHGKHHDTF08xKH8CLIu/uq2juW/g=; b=Z4X/RjV1X2fDp5lNKIDBE9glDI4LQqiAPsS5MurSLXcvjX5s6LJW/6wpUqzQw0emT1 zHBY8ku/2U59yLgX3KdAo9UMJZQJWwxnqPzJe4Iy0PBBOaPAS8YbtL4EU4m9jC99kl8s CxcdWN1+C1+JjbYiNYQ3o38hspMmoD17YKnnE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726249678; x=1726854478; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8IH/fKZ7WlUWd6MAHGKHHDTF08xKH8CLIu/uq2juW/g=; b=IKHlCclLTrM1cBRZdK1eVxIlQ6pP/5pi7TM59uhrpNJgPTg1vmi1xGESLjZpwQhoPV BNxkT1MpPaU6bTMO0ta9gB2usATouos0v5s9g1SIU0twbXJYC9TxMXmuOaeSdjMhyevY kidt3M5/typjntY3gmJ8KgJ+RV9Nq85HXCVzoLoZpxbDc4xzMSraFehPmCOALHY7R15H /fbZ1945uJrN2pvNUDBq0VkVRuy66Q/G/ckdPb6UFcNHpDApehV3axzMkF+HcDV2WyAh 6P7tfvfQUnVw0uVUP5kJzY4yWdSmplNUtORDJktPvpSXeGf/10ofZ3nmd4KGetrMcJfr 6SdA== X-Forwarded-Encrypted: i=1; AJvYcCUa8n/6u4b6g2Tx5YxOw2EKjb9BD3qdpralnYofYKrNkdJx/r0BUzNywefAnb3p3s3S/L8HcB3uT/c=@lists.freedesktop.org X-Gm-Message-State: AOJu0Yy572Y6K0WNqTuRNWLHflTN26VOhB5Eqc3Cr5BogP7QLA50T6bX yzAiucD487uol2dMm83zFD537t+Og79JDw+I/uSAVbeXQfNUuTN4DsgmYSj66A== X-Google-Smtp-Source: AGHT+IF/Z83uZ5DKsWYI6BIBnszLvyBcxjjxnEpt4x8DvN82ruG8ZaQekEMAasgPQ7k4gkSjUIiGcg== X-Received: by 2002:a17:902:c946:b0:207:850c:2548 with SMTP id d9443c01a7336-207850c26e1mr44249585ad.22.1726249677812; Fri, 13 Sep 2024 10:47:57 -0700 (PDT) Received: from localhost ([2a00:79e0:2e14:7:8bb7:9bdd:6697:b2f7]) by smtp.gmail.com with UTF8SMTPSA id d9443c01a7336-2076b01a742sm30385035ad.259.2024.09.13.10.47.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Sep 2024 10:47:57 -0700 (PDT) Date: Fri, 13 Sep 2024 10:47:54 -0700 From: Brian Norris To: Javier Martinez Canillas Cc: Julius Werner , Borislav Petkov , Hugues Bruant , stable@vger.kernel.org, regressions@lists.linux.dev, linux-kernel@vger.kernel.org, Fenghua Yu , Reinette Chatre , Tony Luck , Tzung-Bi Shih , chrome-platform@lists.linux.dev, Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Subject: Re: [NOT A REGRESSION] firmware: framebuffer-coreboot: duplicate device name "simple-framebuffer.0" Message-ID: References: <20240909080200.GAZt6reI9c98c9S_Xc@fat_crate.local> <87jzfhayul.fsf@minerva.mail-host-address-is-not-set> <87mskczv9l.fsf@minerva.mail-host-address-is-not-set> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87mskczv9l.fsf@minerva.mail-host-address-is-not-set> X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" Hi Javier, On Thu, Sep 12, 2024 at 06:33:58PM +0200, Javier Martinez Canillas wrote: > That's a very good point. I'm actually not familiar with Coreboot and I > used an educated guess (in the case of DT for example, that's the main > source of truth and I didn't know if a Core table was in a similar vein). > > Maybe something like the following (untested) patch then? Julius is more familiar with the Coreboot + payload ecosystem than me, but his explanations make sense to me, as does this patch. > From de1c32017006f4671d91b695f4d6b4e99c073ab2 Mon Sep 17 00:00:00 2001 > From: Javier Martinez Canillas > Date: Thu, 12 Sep 2024 18:31:55 +0200 > Subject: [PATCH] firmware: coreboot: Don't register a pdev if screen_info data > is available > > On Coreboot platforms, a system framebuffer may be provided to the Linux > kernel by filling a LB_TAG_FRAMEBUFFER entry in the Coreboot table. But > a Coreboot payload (e.g: SeaBIOS) could also provide this information to > the Linux kernel. > > If that the case, early arch x86 boot code will fill the global struct > screen_info data and that data used by the Generic System Framebuffers > (sysfb) framework to add a platform device with platform data about the > system framebuffer. Normally, these sorts of "early" and "later" ordering descriptions would set alarm bells when talking about independent drivers. But I suppose the "early arch" code has better ordering guaranteeds than drivers, so this should be fine. > But later then the framebuffer_coreboot driver will try to do the same > framebuffer (using the information from the Coreboot table), which will > lead to an error due a simple-framebuffer.0 device already registered: > > sysfs: cannot create duplicate filename '/bus/platform/devices/simple-framebuffer.0' > ... > coreboot: could not register framebuffer > framebuffer coreboot8: probe with driver framebuffer failed with error -17 > > To prevent the issue, make the framebuffer_core driver to not register a > platform device if the global struct screen_info data has been filled. > > Reported-by: Brian Norris > Link: https://lore.kernel.org/all/ZuCG-DggNThuF4pj@b20ea791c01f/T/#ma7fb65acbc1a56042258adac910992bb225a20d2 > Suggested-by: Julius Werner > Signed-off-by: Javier Martinez Canillas > --- > drivers/firmware/google/framebuffer-coreboot.c | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/drivers/firmware/google/framebuffer-coreboot.c b/drivers/firmware/google/framebuffer-coreboot.c > index daadd71d8ddd..4e50da17cd7e 100644 > --- a/drivers/firmware/google/framebuffer-coreboot.c > +++ b/drivers/firmware/google/framebuffer-coreboot.c > @@ -15,6 +15,7 @@ > #include > #include > #include > +#include > > #include "coreboot_table.h" > > @@ -27,6 +28,7 @@ static int framebuffer_probe(struct coreboot_device *dev) > int i; > u32 length; > struct lb_framebuffer *fb = &dev->framebuffer; > + struct screen_info *si = &screen_info; > struct platform_device *pdev; > struct resource res; > struct simplefb_platform_data pdata = { > @@ -36,6 +38,20 @@ static int framebuffer_probe(struct coreboot_device *dev) > .format = NULL, > }; > > + /* > + * If the global screen_info data has been filled, the Generic > + * System Framebuffers (sysfb) will already register a platform Did you mean 'platform_device'? > + * and pass the screen_info as platform_data to a driver that > + * could scan-out using the system provided framebuffer. > + * > + * On Coreboot systems, the advertise LB_TAG_FRAMEBUFFER entry s/advertise/advertised/ ? > + * in the Coreboot table should only be used if the payload did > + * not set video mode info and passed it to the Linux kernel. s/passed/pass/ > + */ > + if (si->orig_video_isVGA == VIDEO_TYPE_VLFB || > + si->orig_video_isVGA == VIDEO_TYPE_EFI) This line is using spaces for indentation. It should use a tab, and then spaces for alignment. But presumably this will change based on Thomas's suggestions anyway. > + return -EINVAL; Is EINVAL right? IIUC, that will print a noisier error to the logs. I believe the "expected" sorts of return codes are ENODEV or ENXIO. (See call_driver_probe().) ENODEV seems like a fine choice, similar to several of the other return codes already used here. Anyway, this seems along the right track. Thanks for tackling, and feel free to carry a: Reviewed-by: Brian Norris > + > if (!fb->physical_address) > return -ENODEV; > > -- > Best regards, > > Javier Martinez Canillas > Core Platforms > Red Hat >