Re: [PATCH v3] i3c: master: fix for SETDASA and DAA process

2020-08-20 Thread Boris Brezillon
On Thu, 20 Aug 2020 21:03:11 +0200 Boris Brezillon wrote: > On Thu, 20 Aug 2020 18:16:14 + > Parshuram Raju Thombare wrote: > > > >Hm, not sure that qualifies as a fix. The current implementation was > > >correct, it was just reserving a slot in the device table for devices > > >that didn't

Re: [PATCH v3] i3c: master: fix for SETDASA and DAA process

2020-08-20 Thread Boris Brezillon
On Thu, 20 Aug 2020 18:16:14 + Parshuram Raju Thombare wrote: > >Hm, not sure that qualifies as a fix. The current implementation was > >correct, it was just reserving a slot in the device table for devices > >that didn't have an init address or on which SETDASA failed. > If I3C controllers

RE: [PATCH v3] i3c: master: fix for SETDASA and DAA process

2020-08-20 Thread Parshuram Raju Thombare
>Hm, not sure that qualifies as a fix. The current implementation was >correct, it was just reserving a slot in the device table for devices >that didn't have an init address or on which SETDASA failed. If I3C controllers like ours use hardware slots to store slave devices info, due to limited ava

Re: [PATCH v3] i3c: master: fix for SETDASA and DAA process

2020-08-20 Thread Boris Brezillon
On Thu, 20 Aug 2020 15:38:26 +0200 Parshuram Thombare wrote: > This patch fix following issue. > Controller slots blocked for devices with static_addr > but no init_dyn_addr may limit the number of I3C devices > on the bus which gets dynamic address in DAA. So > instead of attaching all the devic