From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=194.117.254.33 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795173042; b=46DXv2p4zIkxh/iuORlqvUwX5JU6tpG57oyM0UG4j5ziDk0jsEUxTq9+syIev1RQpZ87 TzzJc10ugub1CSrzn6mSeuukOoZaTjeQeE73Z90x+Bl8Qu+diVxGkb+ayvW4E4UhuqQn8 pzdfmlhshNv1HHqbmxIJthSm29Tq0vGBwjFEjwPlExoB771goqxbKeVS7CqLddHqbcfWB QfvNaHAMiorBhguDPMmyCZ9jEltbJRKinrXI4Jl02wPhBvwMGBGTIq0QcODI2+QHdEGGt Q3LBDqi7Al/kmKxT80EqJyM9q2MI5gzntZ7nBRkHDHa8jKwdyo/U4SRf5wOp7Byu5Vg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795173042; h=DMARC-Filter:DKIM-Signature:Received:Received:X-UD-Smtp-Session:Date: From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type: Content-Disposition:Content-Transfer-Encoding:In-Reply-To; bh=P31KX+HGbOZ2m/ze0RQmiiG2ACd7jzLv4I1BkpYMPf4=; b=gcu03PZjHhXdTfuEUqvu0+xXBBYz2UgvEqauqsCijKXc0TARxVL4m5mCkTAFkbkZN1wr NMxF4bf6fh0PfR7NDhF9LjTDxKDn61IzwAKcTXAYhB/cpBj4QOb5QUin4kX45URMVtwen kRl5zX7ifJFmJ7/K2Ewrc/RwILJaXXMIKzjY+ubmo6RkWbKZxaUv6SpEe5HI8xn961+k0 dFRuAHjpkbqZsNtQT2ZbCH58MwIp3NHS2TIw45q2js5I/0H5faHdJd+kUKBEtLfYzjn8V tAxtY7+cCmkshCz+LT64BHlxy/Nr5YKtVIdExKyMWlarxNJio8Ji80iGMctoUUNjooQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass header.d=sang-engineering.com header.i=@sang-engineering.com header.a=rsa-sha256 header.s=k1 header.b=Obxoi06N; arc=none smtp.remote-ip=194.117.254.33 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 56EEF606A326 for ; Fri, 20 Nov 2026 11:10:38 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 56EEF606A326 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, unprotected) header.d=sang-engineering.com header.i=@sang-engineering.com header.a=rsa-sha256 header.s=k1 header.b=Obxoi06N 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:content-transfer-encoding :in-reply-to; s=k1; bh=P31KX+HGbOZ2m/ze0RQmiiG2ACd7jzLv4I1BkpYMP f4=; b=Obxoi06N2BzJC2E18N5zskewr6CRQuDC+9+KvJKyH9LuFwQeHEoRM8iX+ 1RN3g2hi0vRMpw9ChKCggkqpDtldXjWSxbuf15ors+C79EzQrWROtqkODXwVMioz AwJzyY5VTdwsnFQspH2hE8RSP1Nhf8/y7hf7KJNOdig+td/U5uqFSxRWdKIjksaV xUmXByPF0+tNuh7pm304XaQfgfBSY355NR4ka2paF3JigCsRB5BOfvmbMWMNBP9B GnaFo74Vv47qUVK4+9ZpjQSKFC89PuuUA5BL806XF5TI21wlvLZ+P+r6LUjwEDNL l86k8NVB2qHZ1u6bkApUglRKLQi7w== Received: (qmail 1450248 invoked from network); 20 Nov 2026 12:10:35 +0100 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 20 Nov 2026 12:10:35 +0100 X-UD-Smtp-Session: l3s3148p1@knAOS7Ng4JIujnuU Date: Fri, 20 Nov 2026 12:10:34 +0100 From: Wolfram Sang To: =?utf-8?Q?Cl=C3=A9ment?= Le Goffic Cc: Laurent Pinchart , Geert Uytterhoeven , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Stephen Boyd , Brian Masney , Jerome Brunet , Ulf Hansson , Philipp Zabel , "Rafael J . Wysocki" , Marek Vasut , Bartosz Golaszewski , Konrad Dybcio , Kevin Hilman , Vinod Koul , Kuninori Morimoto , Paul Elder , Sudeep Holla , Cristian Marussi , arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-pm@vger.kernel.org, linux-renesas-soc@vger.kernel.org Subject: Re: [PATCH v5 00/15] R-Car X5H Ironhide CPG/MDLC SCMI remapping support Message-ID: References: <1e9c5ac3-d82b-4af9-9946-0302cadf7404@baylibre.com> <20261119234759.GB2324725@killaraus.ideasonboard.com> <19c3745a-6308-46ff-bb37-3acc88fe22e2@baylibre.com> 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-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <19c3745a-6308-46ff-bb37-3acc88fe22e2@baylibre.com> Hi Clément, > I don't think SCMI itself introduce instability. > It only defines the protocol, and each firmware choose its ids. > Could you tell me what you mean by instability? Let me try to reword: In the past, we wanted to support all kinds of firmware. Sadly, each new firmware introduced different IDs here and there. So, we came up with some stable IDs ourselves and mapped them to the IDs per firmware. This is a n:1-mapping of firmware IDs to our stable IDs. The support for firmware versions got serious opposition from upstream. We concluded that supporting only the latest firmware will make most controversial discussion points vanish. So, we now have a 1:1-mapping of (the latest) firmware IDs to our stable IDs. I guess this is what Geert means with IDs becoming "stable". firmware versions might return IDs, but supporting only one firmware we get the same "stable" ID from it. Sadly, of course, with the next firmware update, we still might get a different ID all the time. So, not stable in that regard and we still need the mapping :( Yes, this means the driver is then tied to a specific firmware version because it only has this mapping. Not nice for a user. But we didn't see another way moving things forward for now. Was this understandable? Geert, did I miss something? Happy hacking everyone, Wolfram