Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp6142486rwd; Wed, 24 May 2023 11:16:20 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4IoG3e84Y6XMYIrnt5xBTM9rhochF2VUAaH6vrLRWPFqvr80fFL+cSUOabdjMf3Etr2gQu X-Received: by 2002:a05:6a00:842:b0:63d:3595:26db with SMTP id q2-20020a056a00084200b0063d359526dbmr4792113pfk.23.1684952179956; Wed, 24 May 2023 11:16:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684952179; cv=none; d=google.com; s=arc-20160816; b=0xqGGVe6Y+Kr7v+LrAYi3nn58dyazX3sXIiUrgqt2XQFMBEMLooftLrH1hVco7EJJ4 oTpoPrdt+yBifpYHySArlYs24aN6oDETasVd4WCcxTmNXXwe1x5JD29MaaC5Mccf1h9l EcubcHoLG/tXgxy/7L9k5r3DjOcI53ECvvq213zEtcsE0tkwEuMXBfxcQKdXAcbnX0Wg pRil1Ns7ea7f0SH0+ba2ELwi8VfeQUDlg1fw+r4o7h5qWBnHmEnjwt8MhrFmCOK2KZYa RDY2bEfpPOHJ16WBREotGtqLODCL67Qvtu8Ga3Ou54DiXmmtTnf0mPo7PvS0so15w3Lo jqZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:subject:cc:to:from:message-id :date:dkim-signature:dkim-signature; bh=jwFVly4kq5P6O0lbSrbMpskCnnMKPILSg3+DmnDJtHM=; b=LUPRNVwXHzWbQJFk9UjOE1WrFB5M7HtCp9538cMyoLhh/b6MGXfCA5ugVKwwl8Cp2v moWB7+RMBqxZN8XKvCkwK2nUnILCnDsRaJl0G9nfWiks42AtqY6M8MaHnTccg8l+9E7J Wrx/ATw9HX2B0wD5L0Ximmq8kJ/s3ZMAjaz13xHn875dM5IFo5NsOubd4ewVmuFJzIYO ccnGEA4MsJsck6V4U6MKPqCI5VEg5PZx4e4P5iC9LvLCRSWNWAM2addQVcih6WGVTu2Y DQNYeUIbBNRJBCnlPmmq7ydq4DGWAMx9mQUaNJ/V5jjzb5Iwt8WDEZHo6chhL32qaKDw WYDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b="W/JGEKPz"; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b=LxmziIUK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a21-20020a63e855000000b00527d158ec6dsi8646277pgk.406.2023.05.24.11.16.07; Wed, 24 May 2023 11:16:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b="W/JGEKPz"; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b=LxmziIUK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235969AbjEXSI0 (ORCPT + 99 others); Wed, 24 May 2023 14:08:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44464 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231260AbjEXSIZ (ORCPT ); Wed, 24 May 2023 14:08:25 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 262ABB6 for ; Wed, 24 May 2023 11:08:24 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id BE05121CF6; Wed, 24 May 2023 18:08:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1684951702; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jwFVly4kq5P6O0lbSrbMpskCnnMKPILSg3+DmnDJtHM=; b=W/JGEKPzGSdFmt/xBO/G+AdQJ1Lk9JJ3bnAxTtHsa8NrfErL9OUyHjbt9FMQ0STCNZzNso iFFNf3ZTtlT6caTNOazuu6fKyuT39u+9qxDiqSjuqgfyCj+k7kBqt+g9hMSJBgxrATdVcu oDsjGO9xUy5Z2Zl206Z7drjppV6EsFM= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1684951702; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jwFVly4kq5P6O0lbSrbMpskCnnMKPILSg3+DmnDJtHM=; b=LxmziIUKjKrDoGdbykUCH3t1MtwcU7rTcuug5MKLe/glVgmQR5vZGBAt8RBl8xx1PD8Ih8 lgNf5mzMkCFUszCw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 5D972133E6; Wed, 24 May 2023 18:08:22 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 2aroFZZSbmSDCwAAMHmgww (envelope-from ); Wed, 24 May 2023 18:08:22 +0000 Date: Wed, 24 May 2023 20:08:21 +0200 Message-ID: <87o7m9d2lm.wl-tiwai@suse.de> From: Takashi Iwai To: Stuart Henderson Cc: Luke Jones , , , , , , , , , , , , , , , , , Subject: Re: CSC3551 and devices missing related _DSD bits In-Reply-To: References: <1991650.PYKUYFuaPT@fedora> <87jzx3zaf8.wl-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 24 May 2023 18:36:04 +0200, Stuart Henderson wrote: > > > > The problem is that this can really easily blow up your machine if > > some incorrect bit is applied. And more easily applicable, more > > chance to break by novice users, simply by believing what a chat bot > > speaks :) > > That's the very reason why this kind of change should be via ACPI > > table officially set up by the vendor. That said, the question is > > only who and how can be responsible for this kind of change. It's > > no technical issue, per se. > > > > If BIOS can't be updated, at least, the configuration change has to be > > confirmed by ASUS people. If ASUS still ignores the inquires and > > requests, we may put the quirk but with a bit fat warning (and maybe > > complaints to ASUS) to be shown in the log as a very last resort. > > > > Let's see what happens. > > Thanks Takashi. > > Just a note to say we're not ignoring this and are investigating the > best way to support released laptops with ACPI incompatible with > Linux.? We're hoping this is going to be less of an issue going > forward.? Please bear with us while we look into this. Good to hear that you're working on it! Sure, it's no urgent issue and better wait for a proper solution. thanks, Takashi