Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp703724ybe; Thu, 5 Sep 2019 04:46:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqyjnyIsVVw+Rgl6CHPZPjKccR83KFzXRv+kygsjm6NElXnXs1sMBmzL8ZtNBD/002sf9LDZ X-Received: by 2002:a17:902:d717:: with SMTP id w23mr2914219ply.321.1567683976739; Thu, 05 Sep 2019 04:46:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567683976; cv=none; d=google.com; s=arc-20160816; b=hTA2LHoL9OQwHUPaiv3HbDAkSjzqFpuhR3S7GsxWCUbHNSgC686VAs7CJ2wXgwnT4z Bi2p0IhH+yzhYBDN9+BVJtv/W8GzHnaddSQcozG1TYHMv/OqZ24pMDFFrPvjrPRz7Hx/ dfTUkouUlXh2pJYBNZ6lEfxNx6mzEIo6lzhfjg5yEq+NFQUQRJBD0PrNWPAwd6OkShSx EF2UXo+o9GM42CiNpmQcaT/5nenlrFdEsupH6e0dT7huu9mtR7d8TTd/TFe/FyruQ3es P7GkfSCgFGLKY0uBQBLg+DtJr1WK0NjuajWs4d2s1rxGICTQOydcfw3beHIDEql4i+B9 enfg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature; bh=NR1UtQzmhDXzelNe/wDAJagqIB/hb2Y47Nfhcrfgy8U=; b=ruBHnA7k/SV/LHyoBNviaVAbeTXD1/07alDpu8I0izHnISjtrfSrHxpknu0EBphZxo YBKH5wyOezAI+uQ4UGGWoQ6fqGCUjQjngpm2s8EKzzAt/NWMi8+ZAcmly6q6Zj9D25e1 nmHwQlCisAtuUkgYlz0ccH71UX38LHi6OfANXTNVmMf4QKVKDwzQzaUSnmbfNkW3/159 WEtewGpnR8a5fi89OJJjvcL/L5nkasoV/FBMhr5C3BivoG3EQodF9OiddPRQYeD5YykA icnUpPSbDM7m5vziYZVwXuQHJQlyJzDMGn6f9ZgISoPjbK9+QzVoUfb/YTK2J/q871q8 5tuw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=ExqotPmX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u21si1572009pgn.290.2019.09.05.04.45.59; Thu, 05 Sep 2019 04:46:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=ExqotPmX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387716AbfIEKAw (ORCPT + 99 others); Thu, 5 Sep 2019 06:00:52 -0400 Received: from smtprelay-out1.synopsys.com ([198.182.47.102]:44176 "EHLO smtprelay-out1.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726115AbfIEKAv (ORCPT ); Thu, 5 Sep 2019 06:00:51 -0400 Received: from mailhost.synopsys.com (mdc-mailhost1.synopsys.com [10.225.0.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by smtprelay-out1.synopsys.com (Postfix) with ESMTPS id 04CEFC0DD3; Thu, 5 Sep 2019 10:00:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=synopsys.com; s=mail; t=1567677651; bh=GosWZM2QU8S12Kgv9mW7HdYKBOJWFoe+3pD+Un3G66o=; h=From:To:Cc:Subject:Date:In-Reply-To:References:In-Reply-To: References:From; b=ExqotPmXtPyrttYl0egCKAjoHy9K3A8M6MiMfU7TFhvGai2DEmP5d1TOunCx7WhsA bX/GnJnv1VfJMFtbFDRdN4gssi2BYXCTPQlYC70C2+asnrlOjoLQ1ZNgyRxIWobJDe rVyL2GEi/k7VN0bRoa6+QT+6F2pPczzRRDSXH7RYBjAj1tl8SBeCIbHd3i+9ysOLZD hE4U3OjOjWVs+wqf70sAlHGL4p5llwvdm1A5ZodZ2N5eHp1LTag1JfbKvxhkeTLgrk 8R+WoNjcQTefQyM8qzXAVM+kK/a860lcqFq4C1w8ozE4F6B6DXLJ7FaTjyO+zeHW0Q ab8UtiEl4ayVg== Received: from de02.synopsys.com (germany.internal.synopsys.com [10.225.17.21]) by mailhost.synopsys.com (Postfix) with ESMTP id 9989BA0061; Thu, 5 Sep 2019 10:00:49 +0000 (UTC) Received: from de02dwia024.internal.synopsys.com (de02dwia024.internal.synopsys.com [10.225.19.81]) by de02.synopsys.com (Postfix) with ESMTP id 826F43F3BC; Thu, 5 Sep 2019 12:00:49 +0200 (CEST) From: Vitor Soares To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-i3c@lists.infradead.org Cc: bbrezillon@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, pgaj@cadence.com, Joao.Pinto@synopsys.com, Vitor Soares Subject: [PATCH v3 4/5] dt-bindings: i3c: add a note for no guarantee of 'assigned-address' use Date: Thu, 5 Sep 2019 12:00:37 +0200 Message-Id: X-Mailer: git-send-email 2.7.4 In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org By default, the framework will try to assign the 'assigned-address' to the device but if the address is already in use the device dynamic address will be different. Signed-off-by: Vitor Soares Reviewed-by: Rob Herring --- Change in v3: - Add Rob rb-tag Documentation/devicetree/bindings/i3c/i3c.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/i3c/i3c.txt b/Documentation/devicetree/bindings/i3c/i3c.txt index c851e75..e777f09 100644 --- a/Documentation/devicetree/bindings/i3c/i3c.txt +++ b/Documentation/devicetree/bindings/i3c/i3c.txt @@ -98,7 +98,9 @@ Required properties Optional properties ------------------- -- assigned-address: dynamic address to be assigned to this device. +- assigned-address: dynamic address to be assigned to this device. The framework + will try to assign this dynamic address but if something + fails the device dynamic address will be different. Example: -- 2.7.4