From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=185.246.85.4 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794989625; b=4CpDUDXIAYPUX4b/IhzVjhTSAo63GF4pP0eZN8FfNmNBvtMNa+/WXpjaYjgY3W2WFxr8 jLXXvvlLFr/cZsl2I/6GjDH58NHmHRuYHBh59rmKEYMRHLIBKiKjZFtbuG6cNYdLoP8AQ 79RyASukRMjcBESgLdhiRMvQLeAVUp3yOma7nalnqigJ66FVHk7PXp89t/nR5RkM8c7z5 7QcmjWdplu6adYN7dwo3hoUXVB/M+VC7k3LWTE5Laq6XjG1rj8Y+dmybhNuit8MoBU+jQ 24z33emqbQGVGK9hixP5rpmax60zli0PaYLxJaKuw7As3M+tdWLiaviwZdi9qIvhv7A== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794989625; h=DMARC-Filter:Received:Received:Received:DKIM-Signature:Date:From:To: Cc:Subject:Message-ID:In-Reply-To:References:Organization:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding: X-Last-TLS-Session-Version; bh=WYyTzxO2ETRiJUcj33BfWavJfCzA6eXVlj29pjh6uOk=; b=pPN6n+dGM/UwBioqZUtHzHspmqzSyy+WjaFegBL062AM3qrzXXjeY/lFfZx4FzMpuaMT 0kJtXtbfI1aaHnPkA/qlS7tTRyTib0YMTsmVrMfKq1bojJdd+10OEOIBbKhoHBlBf1y7L MWiDPSmANpX2IVjt9gN/szLxHimQyt9azVO6o8cTAKDqZ+2lhbtY4cI+UVM1WuuqXTIrJ 3D39UhX3Oa9C8ggXHz/12/+rsV1aQuLfxqLXMiQPjOas8n1watymi/hqYFi7MD4/9MCsX 1JpI2O0BWBqoW+cdwChFZTlM8U4ieUZN2AKkfbfNX+O255zFnyEe+Z6he1hldXe2u5w== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass header.d=bootlin.com header.i=@bootlin.com header.a=rsa-sha256 header.s=dkim header.b=JpUBqGod; arc=none smtp.remote-ip=185.246.85.4 Received: from smtpout-03.galae.net (smtpout-03.galae.net [185.246.85.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 15B93606A330 for ; Wed, 18 Nov 2026 08:13:44 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 15B93606A330 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.a=rsa-sha256 header.s=dkim header.b=JpUBqGod Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-03.galae.net (Postfix) with ESMTPS id 65A944E4160A; Wed, 18 Nov 2026 08:13:43 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 2EA455FE9B; Wed, 18 Nov 2026 08:13:43 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id C022C11BC07B0; Wed, 18 Nov 2026 09:13:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1794989622; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=WYyTzxO2ETRiJUcj33BfWavJfCzA6eXVlj29pjh6uOk=; b=JpUBqGodIl5ANwxil/ZfClbFcF4GJqmoPYauYylAL1OeFCrSY4BOsOFB1uYA7twru1jWRH i+H5bcmdoWe4H/CJ+Nv+8c15EEVxHupjaEuzDjruNlMebQFpsYOILj6Hmj4XP7k+5HAvMD u//04/Mq01Esj/TZIq4zGhujzIHk4+L0+i5Q73Jl/VIzuztupAYVjrcKGHqB+DayZYRFNe i6GZc0a/3Kuag3X8KK+CDn9QubDCPLK1nw0K5YZOpRKeAH0iGfHc3+q6IAlzd0GG2z0zak 2fIitc71vXpZ2aoz7oRGGX4Vy+yn0ePwPodaj4ZtW7L5JXlPfu6DlrQlLoTLhQ== Date: Wed, 18 Nov 2026 09:13:34 +0100 From: Herve Codina To: Svyatoslav Ryhel Cc: Wolfram Sang , Luca Ceresoli , Rob Herring , Andi Shyti , Krzysztof Kozlowski , Conor Dooley , Peter Rosin , =?UTF-8?B?TWljaGHFgiBNaXJvc8WCYXc=?= , Jonas =?UTF-8?B?U2Nod8O2YmVs?= , linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 0/2 RESEND] i2c: muxes: Add GPIO-detected hotplug I2C Message-ID: <20261118091334.3d51a5f0@bootlin.com> In-Reply-To: References: <20251013060018.43851-1-clamor95@gmail.com> <20251021132529.GA4133357-robh@kernel.org> Organization: Bootlin X-Mailer: Claws Mail 4.4.0 (GTK 3.24.52; x86_64-redhat-linux-gnu) X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Last-TLS-Session-Version: TLSv1.3 Hi Svyatoslav, On Sat, 17 Oct 2026 20:17:39 +0300 Svyatoslav Ryhel wrote: > вт, 21 жовт. 2025 р. о 16:25 Rob Herring пише: > > > > On Thu, Oct 16, 2025 at 09:32:24AM +0200, Wolfram Sang wrote: > > > Hi Svyatoslav, > > > > > > > Herve and Luca did not come up with anything meaningful, they provided > > > > just a few rough ideas. It will take an inconsiderate amount of time > > > > > > Well, IIRC they said that your use case can be mapped onto their > > > approach. Which is meaningful in my book. > > > > > > > before there will be any consensus between them and schema > > > > maintainers, and even more time would be requited to settle this into > > > > schemas and implement into drivers. Why should I suffer from this? Why > > > > should changes I need be halted due to some incomplete 'ideas'? This > > > > driver uses existing i2c mux framework and fits into it just fine. > > > > > > I am sorry to bring you bad news, but you need to suffer because this is > > > how development goes. If I get presented a generic solution (see Herve's > > > mail) and a specific solution (your driver), for this case I as a > > > maintainer will prefer the generic solution. Generic solutions need more > > > time because there are more things to handle, of course. This is typical > > > for development, I would say, it is not Linux or Free Software specific. > > > > > > I appreciate that you tackled your issue and were open to share it with > > > the community. I see the work being done there. However, there are so > > > many things going on independently that I can't really prevent double > > > development from happening despite it having a high priority for me. As > > > soon as I get aware of people working on similar issues, I connect them. > > > That's what I did here as well. > > > > > > So, if you want upstream supported I2C hot-plugging, you need to wait > > > for Luca's and Herve's work being accepted. Or provide a superior > > > solution. Or, if you want, join the ride. You already have experience in > > > this field (and hardware plus use case), you would be a very welcome > > > contributor, I would say. > > > > Agreed. > > > > What really slows things down is when there is only 1 user of a new > > binding. Too many times have I accepted one only for the 2nd user to > > show up right after accepting it and wanting something different. So > > now I just require more than 1 user and it is on the submitter(s) to do > > that. After all, it is their itch, not mine. > > > > Rob > > Hello there! > > Were there any advancements with i2c-bus-extension so that I could > finally configure and make my tablet work? Could anyone point me in > the right direction? Thanks. No new advancements. I moved on a prerequisite: Having support for addon format in dtb in order to have support for a list of exported symbols resolution when an dtb is applied on a live devicetree. Anyway, the v3 series [1] need to be updated and a new iteration need to be sent. Also, same operations need to be done on the SPI version [2]. [1] https://lore.kernel.org/all/20250618082313.549140-1-herve.codina@bootlin.com/ [2] https://lore.kernel.org/all/20250729-spi-bus-extension-v1-0-b20c73f2161a@beagleboard.org/ Best regards, Hervé