Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1791508ybe; Tue, 3 Sep 2019 03:37:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqyG+nfCjlt8E8aQ/UOoGScuzpIFVRJm8lDOmDuXVkvSYzzH0aiZqUM0+tmgeBtZpjhUJJAd X-Received: by 2002:a17:902:1e6:: with SMTP id b93mr34359672plb.295.1567507038256; Tue, 03 Sep 2019 03:37:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567507038; cv=none; d=google.com; s=arc-20160816; b=LKodlyVGlgPXsS0Gc8TrdtCJ5pf/FZKVPuo0rhZhQ+ijYmvgFJiE5O0kj41SJIUjrb M5AHJOIs5abGNWewqe7g4uZIiSGsRj6gDzsNIFgBii+lU973Xv8XlGMLeFDPD5DZe7D2 d+maF63XKY6twMfaGi1o+SxNbXotnBuBwiGI500o5pzqzUB+0SzghyZBRZP0C0PyBZQg HrLDCa7lyckRVq4J/nxAeByk7TUDD2Nsq7Du1BkomzBG7aMepDG3jSrZSsOPjsfMMU96 CZvsOIq0QRBFuaXywZ7xtWHTxgij8dTzdgR5FejRgzpNi0ISTe+LyZ6vqxqWwWIdqRDi /2Ag== 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=Xd+inGCF7ypOtdsbBBFcTz/MNSdstUiajKtFE+KCESI=; b=vVjZqGCjhCpzj5nnzmJovHwQ0U0RYH/gXIDMJ6k5XrpflATjPtbk9sD+AmiudVkF5e 6rSVBBJ8GYP8Ef54qAHKXWdNgKpnk0CfOrHfVlIBpGbZ01qErNU3mlB/HfiWaZCtnDTU nU3YXm1F1Rm03OCuLH/A+QdXo1RaBqUM5jwT7caRUJRioX4fXSf5kYdf/vRiaZF10eFf Vk7wm/ulM57PNfqSTHc3j5ZkeJI1njbKgRb3ccc5OOD4TCnmRfWjlexg8X+4w53tOvoZ 4CkEy/+DhhkyGp339YavN6Ac428kT/gqSJ8mk7HGSCwX+Cvovk3JVBhjByR5VPL5DlT6 A1Ow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=CjDt333L; 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 v13si13865833pgr.103.2019.09.03.03.37.01; Tue, 03 Sep 2019 03:37:18 -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=CjDt333L; 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 S1728783AbfICKgC (ORCPT + 99 others); Tue, 3 Sep 2019 06:36:02 -0400 Received: from smtprelay-out1.synopsys.com ([198.182.47.102]:57240 "EHLO smtprelay-out1.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726631AbfICKf7 (ORCPT ); Tue, 3 Sep 2019 06:35:59 -0400 Received: from mailhost.synopsys.com (mdc-mailhost2.synopsys.com [10.225.0.210]) (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 617E6C0C43; Tue, 3 Sep 2019 10:35:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=synopsys.com; s=mail; t=1567506958; bh=8U/YgJ3ZNxmNXa7KrjxfkomJifVMndkP3bF2LzIDNf8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:In-Reply-To: References:From; b=CjDt333L/nT99syog7bhkYL6MGXyuz9V+zVSV314edDeWg5PXKGcSAKbVo7gW7pvl ZbqkszQVVoG923TnaGsvnptH3roxRmrsrnqxqepVsp/fMQPUpoem9GeWwbC57IIXsu E7SzUAJOzOQVOjXcV+MfTN/d5xSbvRPbOf7ZO1cGIFzRTUAXHXyLp+VjjFa0BHkhD7 lFUphqnRW5jEqTX+R3inF9guPjpJqp1R5B5bjtcPlQLfZrPUGwRDxl1zhIdcLuZ1BJ 4k69JxyQb0dQ8D4HupdzaLxmStCGn4JQ1YhhQ5oRX2/aClIt0o1L7fZCFPDruldzc7 KzOpXppK07WjA== Received: from de02.synopsys.com (germany.internal.synopsys.com [10.225.17.21]) by mailhost.synopsys.com (Postfix) with ESMTP id D9A90A005E; Tue, 3 Sep 2019 10:35:56 +0000 (UTC) Received: from de02dwia024.internal.synopsys.com (de02dwia024.internal.synopsys.com [10.225.19.81]) by de02.synopsys.com (Postfix) with ESMTP id C301E3C0DA; Tue, 3 Sep 2019 12:35:56 +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 v2 3/5] dt-bindings: i3c: Make 'assigned-address' valid if static address == 0 Date: Tue, 3 Sep 2019 12:35:52 +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 The I3C devices without a static address can require a specific dynamic address for priority reasons. Let's update the binding document to make the 'assigned-address' property valid if static address == 0 and add an example with this use case. Signed-off-by: Vitor Soares --- Documentation/devicetree/bindings/i3c/i3c.txt | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/i3c/i3c.txt b/Documentation/devicetree/bindings/i3c/i3c.txt index ab729a0..c851e75 100644 --- a/Documentation/devicetree/bindings/i3c/i3c.txt +++ b/Documentation/devicetree/bindings/i3c/i3c.txt @@ -98,9 +98,7 @@ Required properties Optional properties ------------------- -- assigned-address: dynamic address to be assigned to this device. This - property is only valid if the I3C device has a static - address (first cell of the reg property != 0). +- assigned-address: dynamic address to be assigned to this device. Example: @@ -129,6 +127,15 @@ Example: /* * I3C device without a static I2C address but requiring + * specific dynamic address. + */ + sensor@0,39200154004 { + reg = <0x0 0x6072 0x303904d2>; + assigned-address = <0xb>; + }; + + /* + * I3C device without a static I2C address but requiring * resources described in the DT. */ sensor@0,39200154004 { -- 2.7.4