From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 73B5A2FA0DD for ; Wed, 5 Nov 2025 11:51:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762343493; cv=none; b=bpwCnIDVpuncNv5m/VIi24cniREWfcBXkHi5583QTakHV4lf4CoA/jQLgaXEQmR6RVXBWNGRZxEqJVwuscjrWdATlXqVrK7EB6F+iS9JCUNl1TaN2v2Hm7qyXGeXgHljv4vyqfaX68qHKeSK/lK45noW8T3xipwsCf9jEbopUMo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762343493; c=relaxed/simple; bh=0zZZkZEbMwbfbztEt+depDh9rnfDLoVeD2nEyQcZy3k=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=uEHVWh5cLslciEGNzHm+JhOZyUp/gWYI46xvVaoIQthiOcUHIbwd8pZQl/ad7DetOK98UKdPZ9iP6k2rJMkqQ2W2NNsC4W60LLan7KyNWAlwmQmuruWLoaKFeN84LB1ULQV4hHfat5RJtQ4WVO3kDeYE4F/LokFYHSUzoivMhok= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=iXJ+NqGo; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="iXJ+NqGo" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=Ebs8 q+Zhkz66rPrltv/PRIcVR13h8mXvCH9YO5ah/jM=; b=iXJ+NqGo3cRySRjlrr7E DTSdpXkQtzffhxQZ6Q+44owc2Vtwm9M1aOC9GGuyTaQoGh78/pXmk4E02KvyStGq wWxEtoVUy1WnG4DdBg1Dewk7SaAIKNBCG/Uy0732KZL0+qJFl4IDIx1A6/chXGDM sx/S/3Hj60Udx7b1Q1Q9UBoImVljYbWtrffEK2du98YlJQomtG9/1Ggid6AwgYvf TIYavlaRv8KImrPNenMA309ewpCYf4JTy60P2MRrPZIKXWOTGfn2sE2g2fJqeay/ xmYxwqGhUD+rERgsTh7x6Qa4q84mQEtAQNGrbJw6WyI+am/bbvDGQslxtQFjROCM iA== Received: (qmail 3053310 invoked from network); 5 Nov 2025 12:51:24 +0100 Received: by mail.zeus03.de with UTF8SMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 5 Nov 2025 12:51:24 +0100 X-UD-Smtp-Session: l3s3148p1@9OVSkddCDtEujntX Date: Wed, 5 Nov 2025 12:51:23 +0100 From: Wolfram Sang To: "Frank Wunderlich (linux)" Cc: angelogioacchino.delregno@collabora.com, matthias.bgg@kernel.org, Andi Shyti , Qii Wang , Wojciech Siudy , linux-mediatek@lists.infradead.org, linux-i2c@vger.kernel.org, daniel@makrotopia.org Subject: Re: i2c issues in 6.18 on R4, but not r4pro (both mt7988 with i2c-mux on i2c2) Message-ID: References: <3f5ef2d1336933a87d9761b5ff510a1f@fw-web.de> <64fb54d5f2bc929720d3313f7fa2d8cd@fw-web.de> <1144f62ad9886fed60620bce0bbed7ee@fw-web.de> Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > > Maybe this option should be enabled by default or when the i2c-mux is > > selected? > > That's what we were discussing. At least a warning will now get printed > to the logs when booting suggesting the above solution. FYI, all the commits leading to this breakage are reverted now. Sorry for your troubles!