[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR07MB31965A4D52023AE50A26A0DEC1BE0@DM5PR07MB3196.namprd07.prod.outlook.com>
Date: Tue, 12 May 2020 04:57:36 +0000
From: Parshuram Raju Thombare <pthombar@...ence.com>
To: Boris Brezillon <boris.brezillon@...labora.com>
CC: "bbrezillon@...nel.org" <bbrezillon@...nel.org>,
"vitor.soares@...opsys.com" <vitor.soares@...opsys.com>,
Przemyslaw Gaj <pgaj@...ence.com>,
"linux-i3c@...ts.infradead.org" <linux-i3c@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Milind Parab <mparab@...ence.com>,
"praneeth@...com" <praneeth@...com>
Subject: RE: [PATCH v7 2/7] i3c: master: use i3c_master_register only for main
master
>> +/**
>> + * i3c_master_register() - register an I3C master
>
>The function should be renamed and the doc updated to reflect the fact
>that it only works for primary masters:
>
>i3c_primary_master_register() - register a primary I3C master
Sure, I will do that.
>> + * @master: master used to send frames on the bus
>> + * @parent: the parent device (the one that provides this I3C master
>> + * controller)
>> + * @ops: the master controller operations
>> + * @secondary: true if you are registering a secondary master. Will return
>> + * -ENOTSUPP if set to true since secondary masters are not yet
>> + * supported
>
>This argument no longer exists.
Thanks, I missed that comment. It should be removed.
Regards,
Parshuram Thombare
Powered by blists - more mailing lists