Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2109272ybl; Thu, 29 Aug 2019 03:46:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqxE3WeILOSOTopzhB7RcMM7r/YkKBRIgiWITYsMaoWVp9Qr3oyALMYJC6ZGYjQQkPpcF517 X-Received: by 2002:a62:f247:: with SMTP id y7mr10545836pfl.236.1567075581365; Thu, 29 Aug 2019 03:46:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567075581; cv=none; d=google.com; s=arc-20160816; b=N7u74pzoqUuqA7wAEf3h2buf/dtJ+ZeZKi16o61s8fEv6SIAy+qLImCUdKJufsX03Q S1bMe9PUoXZaZefUfcCgie9kE4pdGs7rExLV8nW+zkrecU3Vax7dsfZ9ZPqvkjLEOz8d 4+W8TsmOG1vyMliZo7RltIw4xReatPhC+izAnFaHnt9dm/ccKULGtxJCgANVJXjAYk9t lSLrisS9OKYHSAjn5uMcrd76Crt7+EDzdZE9S6lY0FaMklSoYv5QB7eSCA6u0a7jFjp0 fFu5MKWLKeELZO2p/mMCC9Wqt4k1LVvxmbpGFj8yKBapkrWxVD2qgQaarW+Q21532l4n OCiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=/ijndbaiIaqXWs1Q5CAOSZrOl9o77Uw1goj5zpm3yQE=; b=if35YQIFVyi2CzgYkl9n+15gX4heuy6e6N6WkwSwZz6A3GlwOUtpMYcFm6qnAW0IuP wjNZvXZSW2o6v72e2AIGznHROxjqWGHvY7HMZinhn1Oy/oEgVZIqoxR9RTpZgMAxG+G3 68dvJkPxLjzlHgGscW4OHHivcG6vXL1L7Oky/A/5ysV746yohGNf4aJNO1M/t510412B ps98qtGYVu0fjTwEiEdglgHzP20Vej12cGtxSYZuhsgfp105bRSwwfkW+YCrpbfNRmo/ oXDGkjeepNLeAPIi7s5tq6mwnHtcUJBMRRos8UvfLlkGbJkIvqKkNnoxemth0kDWTFu8 V4vg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j1si1586364plk.55.2019.08.29.03.46.05; Thu, 29 Aug 2019 03:46:21 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727001AbfH2KpF (ORCPT + 99 others); Thu, 29 Aug 2019 06:45:05 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:59598 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726416AbfH2KpF (ORCPT ); Thu, 29 Aug 2019 06:45:05 -0400 Received: from localhost (unknown [IPv6:2a01:e0a:2c:6930:5cf4:84a1:2763:fe0d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bbrezillon) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 85BB928626E; Thu, 29 Aug 2019 11:45:02 +0100 (BST) Date: Thu, 29 Aug 2019 12:44:57 +0200 From: Boris Brezillon To: Vitor Soares Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-i3c@lists.infradead.org, bbrezillon@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, Joao.Pinto@synopsys.com Subject: Re: [PATCH 2/4] i3c: master: Check if devices have i3c_dev_boardinfo on i3c_master_add_i3c_dev_locked() Message-ID: <20190829124457.3a750932@collabora.com> In-Reply-To: <3e21481ddf53ea58f5899df6ec542b79b8cbcd68.1567071213.git.vitor.soares@synopsys.com> References: <3e21481ddf53ea58f5899df6ec542b79b8cbcd68.1567071213.git.vitor.soares@synopsys.com> Organization: Collabora X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 Aug 2019 12:19:33 +0200 Vitor Soares wrote: > The I3C devices described in DT might not be attached to the master which > doesn't allow to assign a specific dynamic address. I remember testing this when developing the framework, so, unless another patch regressed it, it should already work. I suspect patch 1 is actually the regressing this use case. > > This patch check if a device has i3c_dev_boardinfo and add it to > i3c_dev_desc structure. In this conditions, the framework will try to > assign the i3c_dev_boardinfo->init_dyn_addr even if stactic address = 0. > > Signed-off-by: Vitor Soares > --- > drivers/i3c/master.c | 22 ++++++++++++++++++++++ > 1 file changed, 22 insertions(+) > > diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c > index 4d29e1f..85fbda6 100644 > --- a/drivers/i3c/master.c > +++ b/drivers/i3c/master.c > @@ -1795,6 +1795,23 @@ i3c_master_search_i3c_dev_duplicate(struct i3c_dev_desc *refdev) > return NULL; > } > > +static struct i3c_dev_boardinfo * > +i3c_master_search_i3c_boardinfo(struct i3c_dev_desc *dev) > +{ > + struct i3c_master_controller *master = i3c_dev_get_master(dev); > + struct i3c_dev_boardinfo *boardinfo; > + > + if (dev->boardinfo) > + return NULL; > + > + list_for_each_entry(boardinfo, &master->boardinfo.i3c, node) { > + if (dev->info.pid == boardinfo->pid) > + return boardinfo; > + } > + > + return NULL; > +} > + > /** > * i3c_master_add_i3c_dev_locked() - add an I3C slave to the bus > * @master: master used to send frames on the bus > @@ -1816,6 +1833,7 @@ int i3c_master_add_i3c_dev_locked(struct i3c_master_controller *master, > { > struct i3c_device_info info = { .dyn_addr = addr }; > struct i3c_dev_desc *newdev, *olddev; > + struct i3c_dev_boardinfo *boardinfo; > u8 old_dyn_addr = addr, expected_dyn_addr; > struct i3c_ibi_setup ibireq = { }; > bool enable_ibi = false; > @@ -1875,6 +1893,10 @@ int i3c_master_add_i3c_dev_locked(struct i3c_master_controller *master, > if (ret) > goto err_detach_dev; > > + boardinfo = i3c_master_search_i3c_boardinfo(newdev); > + if (boardinfo) > + newdev->boardinfo = boardinfo; > + > /* > * Depending on our previous state, the expected dynamic address might > * differ: