From: Boris Brezillon <boris.brezillon@collabora.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Parshuram Thombare <pthombar@cadence.com>,
<bbrezillon@kernel.org>, <vitor.soares@synopsys.com>,
<pgaj@cadence.com>, <linux-i3c@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <mparab@cadence.com>,
<praneeth@ti.com>
Subject: Re: [PATCH v2 1/2] i3c: master add i3c_master_attach_boardinfo to preserve boardinfo
Date: Fri, 29 May 2020 16:42:14 +0200 [thread overview]
Message-ID: <20200529164214.49ba670c@collabora.com> (raw)
In-Reply-To: <1590053542-389-1-git-send-email-pthombar@cadence.com>
On Thu, 21 May 2020 11:32:22 +0200
Parshuram Thombare <pthombar@cadence.com> wrote:
> Boardinfo was lost if I3C object for devices with boardinfo
> available are not created or not added to the I3C device list
> because of some failure e.g. SETDASA failed, retrieve info failed etc
> This patch adds i3c_master_attach_boardinfo which scan boardinfo list
> in the master object and 'attach' it to the I3C device object.
>
> Fixes: 3a379bbcea0a ("i3c: Add core I3C infrastructure")
> Signed-off-by: Parshuram Thombare <pthombar@cadence.com>
This patch looks good to me. I'll apply it just after the merge window.
> ---
> drivers/i3c/master.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
> index 5f4bd52121fe..3d995f247cb7 100644
> --- a/drivers/i3c/master.c
> +++ b/drivers/i3c/master.c
> @@ -1776,6 +1776,21 @@ static void i3c_master_bus_cleanup(struct i3c_master_controller *master)
> i3c_master_detach_free_devs(master);
> }
>
> +static void i3c_master_attach_boardinfo(struct i3c_dev_desc *i3cdev)
> +{
> + struct i3c_master_controller *master = i3cdev->common.master;
> + struct i3c_dev_boardinfo *i3cboardinfo;
> +
> + list_for_each_entry(i3cboardinfo, &master->boardinfo.i3c, node) {
> + if (i3cdev->info.pid != i3cboardinfo->pid)
> + continue;
> +
> + i3cdev->boardinfo = i3cboardinfo;
> + i3cdev->info.static_addr = i3cboardinfo->static_addr;
> + return;
> + }
> +}
> +
> static struct i3c_dev_desc *
> i3c_master_search_i3c_dev_duplicate(struct i3c_dev_desc *refdev)
> {
> @@ -1831,10 +1846,10 @@ int i3c_master_add_i3c_dev_locked(struct i3c_master_controller *master,
> if (ret)
> goto err_detach_dev;
>
> + i3c_master_attach_boardinfo(newdev);
> +
> olddev = i3c_master_search_i3c_dev_duplicate(newdev);
> if (olddev) {
> - newdev->boardinfo = olddev->boardinfo;
> - newdev->info.static_addr = olddev->info.static_addr;
> newdev->dev = olddev->dev;
> if (newdev->dev)
> newdev->dev->desc = newdev;
next prev parent reply other threads:[~2020-05-29 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 9:31 [PATCH v2 0/2] I3C SETDASA and DAA process fix Parshuram Thombare
2020-05-21 9:32 ` [PATCH v2 1/2] i3c: master add i3c_master_attach_boardinfo to preserve boardinfo Parshuram Thombare
2020-05-29 14:42 ` Boris Brezillon [this message]
2020-05-21 9:33 ` [PATCH v2 2/2] i3c: master: fix for SETDASA and DAA process Parshuram Thombare
2020-08-19 8:12 ` Boris Brezillon
2020-08-20 9:23 ` Parshuram Raju Thombare
2020-08-20 9:47 ` Boris Brezillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200529164214.49ba670c@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mparab@cadence.com \
--cc=pgaj@cadence.com \
--cc=praneeth@ti.com \
--cc=pthombar@cadence.com \
--cc=vitor.soares@synopsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).