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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 325C0C77B73 for ; Wed, 24 May 2023 18:08:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235993AbjEXSI2 (ORCPT ); Wed, 24 May 2023 14:08:28 -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 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