[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5c2049cc-05aa-1f5b-65af-4df1147ed56a@synopsys.com>
Date: Thu, 26 Jan 2017 11:49:59 +0000
From: Luis Oliveira <Luis.Oliveira@...opsys.com>
To: Wolfram Sang <wsa@...-dreams.de>,
Luis Oliveira <Luis.Oliveira@...opsys.com>
CC: <robh+dt@...nel.org>, <mark.rutland@....com>,
<jarkko.nikula@...ux.intel.com>,
<andriy.shevchenko@...ux.intel.com>,
<mika.westerberg@...ux.intel.com>, <linux-i2c@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<vz@...ia.com>, <Ramiro.Oliveira@...opsys.com>,
<Joao.Pinto@...opsys.com>, <CARLOS.PALMINHA@...opsys.com>
Subject: Re: [PATCH v3] i2c: core: helper function to detect slave mode
On 25-Jan-17 20:45, Wolfram Sang wrote:
>
>> + * i2c_slave_mode_detect - detect operation mode
>
> I'd rather name it 'i2c_detect_slave_mode'
I will do a V4 with this change.
>
>> + * @dev: The device owning the bus
>> + *
>> + * This checks the device nodes for an I2C slave by checking the address
>> + * used.
>> + *
>> + * Returns true if an I2C slave is detected, otherwise returns false.
>
> Both paragraphs could be a little more explicit. It is not about
> "slaves" or "clients" in general, but about those entries which make the
> current master act as a slave, too.
>
Ok, I see your point of view. I will reword it also.
> The code looks good to me, so we are close to go!
>
> Thanks,
>
> Wolfram
>
Great! Thanks
Powered by blists - more mailing lists