From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from codeconstruct.com.au (pi.codeconstruct.com.au [203.29.241.158]) (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 B7F3A16089A; Wed, 26 Jun 2024 10:24:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=203.29.241.158 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719397458; cv=none; b=Rc0cSSuMBek4gTTYjXW99hTiGIsjmdKcrYy5ASk99mXBUuVytESV6upJ/TblI7mx6jLnk+Ab1fTTNseb7usqOm+qTwoTmrFh8KZqouTjInjg3GXW9sf8yBvOtS4M0AvfeofFQxa4sNFCKpoHomYaHHiOW3q9ClnBptOmVax0uRE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719397458; c=relaxed/simple; bh=Z9OEb+W758nrFwD4DhnTTZ3Php5ucgAJEIdfGNrKUnY=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=ZsQiv1EXSyP9aRb+U6qHLjybAC317psujhYIaFuplzeb6/rLK04Wtyn74xazF5UuOqSQkDoZsAAo64AC7Um+fO4D4s28Um5b+c0uEfKB8GyaR2Vfscs3GfXbHsxbahxc5IxbvzpjbOl9PFBtKZIoABsjRzEHQdvo8a4/5+18GAg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=codeconstruct.com.au; spf=pass smtp.mailfrom=codeconstruct.com.au; dkim=pass (2048-bit key) header.d=codeconstruct.com.au header.i=@codeconstruct.com.au header.b=ZMkT1QN8; arc=none smtp.client-ip=203.29.241.158 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=codeconstruct.com.au Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=codeconstruct.com.au Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=codeconstruct.com.au header.i=@codeconstruct.com.au header.b="ZMkT1QN8" Received: from pecola.lan (unknown [159.196.93.152]) by mail.codeconstruct.com.au (Postfix) with ESMTPSA id 16D50200EE; Wed, 26 Jun 2024 18:24:14 +0800 (AWST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codeconstruct.com.au; s=2022a; t=1719397454; bh=Z9OEb+W758nrFwD4DhnTTZ3Php5ucgAJEIdfGNrKUnY=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=ZMkT1QN8UFT0Fak1pLNlBYR6DfHHiVP7NAtk5ixPxEbOhlTV+BU+KVQQkiuZlfdaW B9p5nM8pzH9wkTX2ZcU6/3iNY4qBxZfAE/mPXSrbsLNcFGb5GhmAzOgrCtz1jA/XNb z7OyzlaWcPTXOiq9Cua1Gp3Si+KWkLbaOly3/2j9NxG/M+tkWBXKwpxciRserA0tDk BzLtYRwFmWlCh+qHSsi/VsFkoUy6kZYUY+vdVPoF+t112z0bK3/NC7qGPxAFPIQ+s5 zt3uR9bbUedpsMFPDT/XlhKjQpusDxbXX8m24SHWhy+40UJWdTav8KZKU+8klIKQdB QAjLCgQ0thUug== Message-ID: Subject: Re: [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops From: Jeremy Kerr To: "Aniket ." Cc: Krzysztof Kozlowski , Alexandre Belloni , Joel Stanley , Billy Tsai , Rob Herring , Krzysztof Kozlowski , linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Date: Wed, 26 Jun 2024 18:24:13 +0800 In-Reply-To: References: <20240626052238.1577580-1-aniketmaurya@google.com> <20240626052238.1577580-2-aniketmaurya@google.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4-2 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Hi Aniket, > I am using dw core directly through Synopsys virtualizer development > kit(VDK) setup. Does that mean that *all* existing implementations of this design will have IBI support? Changing this in the pre-existing driver will be asserting that. > Shall I remove the ibi_capable property from the dw_i3c_master > struct? Only if you can ensure it's not going to break the driver for existing hardware deployments. Cheers, Jeremy