From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fllvem-ot04.ext.ti.com (fllvem-ot04.ext.ti.com [198.47.19.246]) (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 11CEC134B0 for ; Fri, 24 Jan 2025 14:33:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.19.246 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737729194; cv=none; b=fFNO4uMCl9QgVhl9zSzdiGIYgctpPaNzdgIKPBCENP/MAikmQFQQCuxpyJj57DuKRQawIcb2EjIPiA5Jm+XVueT9E2U/0q/sCsQkdCjIrPFI+cFXKQqx4eKtWlx8IKHbkxWivtmDeDEAK0hfiWpM79vnQYArV3QW564ifUDj7X4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737729194; c=relaxed/simple; bh=Qr4MG/UqB9khN1eVH4cBqQszcEatvnxOpPlOfTRYctA=; h=Date:From:To:CC:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=E2C6sCIhZrhqzyK/Mqpvb5N9gf63BoY0tPkunedfWQjMPczJOowQ3CeCaPAkmuXcpaKfPf8+FHkipkbJ1+hijieiXCUqlaZFo3BrRUxrPMMsknIcS1XV/gBhYXaME/q23Ok79japvIUqoz6cU9li+Cb2NHfEc8wzPNzOOdLfwN8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=ghjUFmrX; arc=none smtp.client-ip=198.47.19.246 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="ghjUFmrX" Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllvem-ot04.ext.ti.com (8.15.2/8.15.2) with ESMTPS id 50OEX23n562381 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 24 Jan 2025 08:33:02 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1737729182; bh=4K2RsbBndc2+LiHOhzIV4NiFTNlm1huFH4g+eHLfKSY=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=ghjUFmrXc+/MYlN0z6vUZ0a5uTaUTihSCuh1lYfKOn9mVwcHCwLqzXZ4gQyX1AQVC d1VlzA6q9P9U37UNNWhMI1WTcLWE6ABq4TjMbBp7ZLdLwzREt2ocTQNf41Z1SiVGn0 GTqojvMyqK0aiFdRvKQ10nrJarhisSvsCv2MrOmc= Received: from DFLE108.ent.ti.com (dfle108.ent.ti.com [10.64.6.29]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 50OEX2Tn085913 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 24 Jan 2025 08:33:02 -0600 Received: from DFLE109.ent.ti.com (10.64.6.30) by DFLE108.ent.ti.com (10.64.6.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Fri, 24 Jan 2025 08:33:01 -0600 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Fri, 24 Jan 2025 08:33:01 -0600 Received: from localhost (uda0133052.dhcp.ti.com [128.247.81.232]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 50OEX1iw028616; Fri, 24 Jan 2025 08:33:01 -0600 Date: Fri, 24 Jan 2025 08:33:01 -0600 From: Nishanth Menon To: Greg Kroah-Hartman CC: Andrew Davis , Peter Rosin , Vignesh Raghavendra , , "Rob Herring (Arm)" , Lee Jones Subject: Re: [PATCH] mux: mmio: Do not use syscon helper to build regmap Message-ID: <20250124143301.om526lwkvcw2hmq5@shaping> References: <20250123182059.597491-1-afd@ti.com> <20250123200412.6zuhlbz4zorazdhq@deport> <2025012446-unturned-frugality-7a20@gregkh> Precedence: bulk X-Mailing-List: linux-kernel@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: <2025012446-unturned-frugality-7a20@gregkh> X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea On 06:26-20250124, Greg Kroah-Hartman wrote: [...] > > Greg, Peter, > > > > This is part of the fixes TI K3 platforms boot issues reported in > > https://lore.kernel.org/all/b2413460-ec8b-4c77-99b8-4c32b262439a@ti.com/ > > on the latest linus master v6.13-5001-gd0d106a2bd21 + linux > > next-20250123 > > > > Total set of patches tested with: > > https://lore.kernel.org/all/20250119182121.3956546-1-vaishnav.a@ti.com/ > > https://lore.kernel.org/r/20250123181726.597144-1-afd@ti.com > > https://lore.kernel.org/r/20250123181913.597304-1-afd@ti.com > > https://lore.kernel.org/r/20250123182059.597491-1-afd@ti.com > > https://lore.kernel.org/r/20250123182234.597665-1-afd@ti.com > > > > Could we get this routed to master as fixes asap please to get a sane 6.14? > > Our trees are of course closed right now due to the merge window, you > know that :) Yes, of course. > > So we can take things after -rc1 is out, and route bugfixes for > 6.14-final and new stuff for 6.15-rc1, like always. It's hard to see > that this is just a bugfix, but if it is, it needs a Fixes: tag at the > very least, right? I am not entirely sure which commit to use for fixes. On one hand, we can use https://lore.kernel.org/all/b2413460-ec8b-4c77-99b8-4c32b262439a@ti.com/ as the cause of the Fixes. Since, the change in behavior of the subsystem late in the merge cycle caused this side effect, but, we could argue that this patch fixes the subsystem for it's intended behavior and unfortunately exposed issues in users of the syscon subsystem depending on the "wrong" behavior. OR The code introduced long back which depended on the older syscon behavior. but, then, we can argue that it was working fine at that point.. and if we cherry-pick the fixup for stable, it is probably inaccurate for the syscon behavior in older kernels? Lee, Rob: Could you chime in with your suggestion? -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D