| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20190904044718.GB23588@global.cadence.com>
Date: Wed, 4 Sep 2019 05:47:18 +0100
From: Przemyslaw Gaj <pgaj@...ence.com>
To: Vitor Soares <Vitor.Soares@...opsys.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-i3c@...ts.infradead.org" <linux-i3c@...ts.infradead.org>,
"bbrezillon@...nel.org" <bbrezillon@...nel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"Joao.Pinto@...opsys.com" <Joao.Pinto@...opsys.com>,
Rafal Ciepiela <rafalc@...ence.com>
Subject: Re: [PATCH v2 1/5] i3c: master: detach and free device if
pre_assign_dyn_addr() fails
The 09/03/2019 11:57, Vitor Soares wrote:
> EXTERNAL MAIL
>
>
> From: Przemyslaw Gaj <pgaj@...ence.com>
> Date: Tue, Sep 03, 2019 at 12:13:57
>
> > Hi Vitor,
> >
> > I'm sorry for the delay.
> >
> > The 09/03/2019 12:35, Vitor Soares wrote:
> > > EXTERNAL MAIL
> > >
> > >
> > > On pre_assing_dyn_addr() the devices that fail:
> > > i3c_master_setdasa_locked()
> > > i3c_master_reattach_i3c_dev()
> > > i3c_master_retrieve_dev_info()
> > >
> > > are kept in memory and master->bus.devs list. This makes the i3c devices
> > > without a dynamic address are sent on DEFSLVS CCC command. Fix this by
> > > detaching and freeing the devices that fail on pre_assign_dyn_addr().
> >
> > What is the problem with sending devices without dynamic address in DEFSLVS?
>
> How do you address them?
> For the DA field in DEFSLVS frame, the spec says: "shall contain the
> current value of the Slave's assigned 7-bit Dynamic address". If the
> device doesn't have the dynamic address assigned yet why send it?
>
What stops us from operating with this device in I2C mode using his SA?
> > Shouldn't we still inform rest of the devices about that? About fact that
> > device with SA without DA exists on the bus?
>
> I would like to understand what is the use case for this?
Look above. I2C mode still should be possible IMO. Just consider the case when
you really need some information from that device, main master can assign
dynamic address later but you can make some transfers. I know our framework
does not support that case but secondary master can be different system which
should know that this device exists and don't have DA yet, so I2C mode is
available.
>
> On I3C spec table "I3C Devices Roles vs Responsibilities", Secondary
> Master is not responsible to do Dynamic Address Assignment but it is
> optional to do Hot-Join Dynamic Address Assignment.
>
Yes, we discussed that few times during the review of Mastership patch series.
> >
> > I think that this is limitation for us. Espacially we have SA and DA fields in
> > DEFSLVS frame so we are able to distinguish devices with and without Dynamic
> > Address.
>
> I would say the reason behind is regarding how to distinguish i2c from
> i3c devices.
>
> >
> > >
> > > Signed-off-by: Vitor Soares <vitor.soares@...opsys.com>
> > > ---
> > > Changes in v2:
> > > - Move out detach/free the i3c_dev_desc from pre_assign_dyn_addr()
> > > - Convert i3c_master_pre_assign_dyn_addr() to return an int
> > >
> > > drivers/i3c/master.c | 22 +++++++++++++++-------
> > > 1 file changed, 15 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
> > > index 5f4bd52..586e34f 100644
> > > --- a/drivers/i3c/master.c
> > > +++ b/drivers/i3c/master.c
> > > @@ -1426,19 +1426,19 @@ static void i3c_master_detach_i2c_dev(struct i2c_dev_desc *dev)
> > > master->ops->detach_i2c_dev(dev);
> > > }
> > >
> > > -static void i3c_master_pre_assign_dyn_addr(struct i3c_dev_desc *dev)
> > > +static int i3c_master_pre_assign_dyn_addr(struct i3c_dev_desc *dev)
> > > {
> > > struct i3c_master_controller *master = i3c_dev_get_master(dev);
> > > int ret;
> > >
> > > if (!dev->boardinfo || !dev->boardinfo->init_dyn_addr ||
> > > !dev->boardinfo->static_addr)
> > > - return;
> > > + return 0;
> > >
> > > ret = i3c_master_setdasa_locked(master, dev->info.static_addr,
> > > dev->boardinfo->init_dyn_addr);
> > > if (ret)
> > > - return;
> > > + return ret;
> > >
> > > dev->info.dyn_addr = dev->boardinfo->init_dyn_addr;
> > > ret = i3c_master_reattach_i3c_dev(dev, 0);
> > > @@ -1449,10 +1449,12 @@ static void i3c_master_pre_assign_dyn_addr(struct i3c_dev_desc *dev)
> > > if (ret)
> > > goto err_rstdaa;
> > >
> > > - return;
> > > + return 0;
> > >
> > > err_rstdaa:
> > > i3c_master_rstdaa_locked(master, dev->boardinfo->init_dyn_addr);
> > > +
> > > + return ret;
> > > }
> > >
> > > static void
> > > @@ -1647,7 +1649,7 @@ static int i3c_master_bus_init(struct i3c_master_controller *master)
> > > enum i3c_addr_slot_status status;
> > > struct i2c_dev_boardinfo *i2cboardinfo;
> > > struct i3c_dev_boardinfo *i3cboardinfo;
> > > - struct i3c_dev_desc *i3cdev;
> > > + struct i3c_dev_desc *i3cdev, *i3ctmp;
> > > struct i2c_dev_desc *i2cdev;
> > > int ret;
> > >
> > > @@ -1746,8 +1748,14 @@ static int i3c_master_bus_init(struct i3c_master_controller *master)
> > > * Pre-assign dynamic address and retrieve device information if
> > > * needed.
> > > */
> > > - i3c_bus_for_each_i3cdev(&master->bus, i3cdev)
> > > - i3c_master_pre_assign_dyn_addr(i3cdev);
> > > + list_for_each_entry_safe(i3cdev, i3ctmp, &master->bus.devs.i3c,
> > > + common.node) {
> > > + ret = i3c_master_pre_assign_dyn_addr(i3cdev);
> > > + if (ret) {
> > > + i3c_master_detach_i3c_dev(i3cdev);
> > > + i3c_master_free_i3c_dev(i3cdev);
> > > + }
> > > + }
> > >
> > > ret = i3c_master_do_daa(master);
> > > if (ret)
> > > --
> > > 2.7.4
> > >
> >
> > --
> > --
> > Przemyslaw Gaj
>
> Best regards,
> Vitor Soares
--
--
Przemyslaw Gaj
Powered by blists - more mailing lists