From: Pierre Yves MORDRET <pierre-yves.mordret@st.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/6] i2c: i2c-stm32f7: Add 10-bit address support
Date: Mon, 26 Mar 2018 09:56:40 +0200 [thread overview]
Message-ID: <fd463a3d-354c-d4e9-16a8-2829ccc04adc@st.com> (raw)
In-Reply-To: <20180324224332.apsixpklrgtelak7@ninjato>
On 03/24/2018 11:43 PM, Wolfram Sang wrote:
> On Wed, Mar 21, 2018 at 05:48:55PM +0100, Pierre-Yves MORDRET wrote:
>> This patch adds support for 10-bit device address for STM32F7 I2C
>>
>> Signed-off-by: M'boumba Cedric Madianga <cedric.madianga@gmail.com>
>> Signed-off-by: Pierre-Yves MORDRET <pierre-yves.mordret@st.com>
>
> Out of curiosity: how did you test this patch? I never managed to find a
> 10-bit client (except for an SoC with 10-bit slave mode).
I don't have a 10-bit device either. For testing 10-bit I'm using 2 I2C
instances from the SoC, one in master mode and the other in slave mode.
>
>> ---
>> Version history:
>> v1:
>> * Initial
>> v2:
>> ---
>> ---
>> drivers/i2c/busses/i2c-stm32f7.c | 22 +++++++++++++++++-----
>> 1 file changed, 17 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-stm32f7.c b/drivers/i2c/busses/i2c-stm32f7.c
>> index f273e28..ae0d15c 100644
>> --- a/drivers/i2c/busses/i2c-stm32f7.c
>> +++ b/drivers/i2c/busses/i2c-stm32f7.c
>> @@ -65,7 +65,12 @@
>> #define STM32F7_I2C_CR2_NACK BIT(15)
>> #define STM32F7_I2C_CR2_STOP BIT(14)
>> #define STM32F7_I2C_CR2_START BIT(13)
>> +#define STM32F7_I2C_CR2_HEAD10R BIT(12)
>> +#define STM32F7_I2C_CR2_ADD10 BIT(11)
>> #define STM32F7_I2C_CR2_RD_WRN BIT(10)
>> +#define STM32F7_I2C_CR2_SADD10_MASK GENMASK(9, 0)
>> +#define STM32F7_I2C_CR2_SADD10(n) (((n) & \
>> + STM32F7_I2C_CR2_SADD10_MASK))
>> #define STM32F7_I2C_CR2_SADD7_MASK GENMASK(7, 1)
>> #define STM32F7_I2C_CR2_SADD7(n) (((n) & 0x7f) << 1)
>>
>> @@ -176,14 +181,14 @@ struct stm32f7_i2c_timings {
>>
>> /**
>> * struct stm32f7_i2c_msg - client specific data
>> - * @addr: 8-bit slave addr, including r/w bit
>> + * @addr: 8-bit or 10-bit slave addr, including r/w bit
>> * @count: number of bytes to be transferred
>> * @buf: data buffer
>> * @result: result of the transfer
>> * @stop: last I2C msg to be sent, i.e. STOP to be generated
>> */
>> struct stm32f7_i2c_msg {
>> - u8 addr;
>> + u16 addr;
>> u32 count;
>> u8 *buf;
>> int result;
>> @@ -629,8 +634,15 @@ static void stm32f7_i2c_xfer_msg(struct stm32f7_i2c_dev *i2c_dev,
>> cr2 |= STM32F7_I2C_CR2_RD_WRN;
>>
>> /* Set slave address */
>> - cr2 &= ~STM32F7_I2C_CR2_SADD7_MASK;
>> - cr2 |= STM32F7_I2C_CR2_SADD7(f7_msg->addr);
>> + cr2 &= ~(STM32F7_I2C_CR2_HEAD10R | STM32F7_I2C_CR2_ADD10);
>> + if (msg->flags & I2C_M_TEN) {
>> + cr2 &= ~STM32F7_I2C_CR2_SADD10_MASK;
>> + cr2 |= STM32F7_I2C_CR2_SADD10(f7_msg->addr);
>> + cr2 |= STM32F7_I2C_CR2_ADD10;
>> + } else {
>> + cr2 &= ~STM32F7_I2C_CR2_SADD7_MASK;
>> + cr2 |= STM32F7_I2C_CR2_SADD7(f7_msg->addr);
>> + }
>>
>> /* Set nb bytes to transfer and reload if needed */
>> cr2 &= ~(STM32F7_I2C_CR2_NBYTES_MASK | STM32F7_I2C_CR2_RELOAD);
>> @@ -798,7 +810,7 @@ static int stm32f7_i2c_xfer(struct i2c_adapter *i2c_adap,
>>
>> static u32 stm32f7_i2c_func(struct i2c_adapter *adap)
>> {
>> - return I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL;
>> + return I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL | I2C_FUNC_10BIT_ADDR;
>> }
>>
>> static struct i2c_algorithm stm32f7_i2c_algo = {
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2018-03-26 7:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 16:48 [PATCH v2 0/6] Add different features for I2C Pierre-Yves MORDRET
2018-03-21 16:48 ` [PATCH v2 1/6] i2c: i2c-stm32f7: Add 10-bit address support Pierre-Yves MORDRET
2018-03-24 22:43 ` Wolfram Sang
2018-03-26 7:56 ` Pierre Yves MORDRET [this message]
2018-03-26 8:00 ` Wolfram Sang
2018-03-21 16:48 ` [PATCH v2 2/6] i2c: i2c-stm32f7: Add slave support Pierre-Yves MORDRET
2018-03-25 18:16 ` Wolfram Sang
2018-03-26 8:41 ` Pierre Yves MORDRET
2018-04-03 15:26 ` Wolfram Sang
2018-04-04 8:13 ` Pierre Yves MORDRET
2018-04-04 11:07 ` Wolfram Sang
2018-03-21 16:48 ` [PATCH v2 3/6] i2c: i2c-stm32f7: Add initial SMBus protocols support Pierre-Yves MORDRET
2018-03-24 22:49 ` Wolfram Sang
2018-03-26 8:13 ` Pierre Yves MORDRET
2018-04-03 15:31 ` Wolfram Sang
2018-04-04 8:16 ` Pierre Yves MORDRET
2018-04-04 9:04 ` Pierre Yves MORDRET
2018-04-27 20:48 ` Wolfram Sang
2018-03-21 16:48 ` [PATCH v2 4/6] i2c: i2c-stm32: Add generic DMA API Pierre-Yves MORDRET
2018-03-24 22:51 ` Wolfram Sang
2018-03-26 8:20 ` Pierre Yves MORDRET
2018-03-21 16:48 ` [PATCH v2 5/6] i2c: i2c-stm32f7: Add DMA support Pierre-Yves MORDRET
2018-04-03 15:39 ` Wolfram Sang
2018-04-04 8:20 ` Pierre Yves MORDRET
2018-03-21 16:49 ` [PATCH v2 6/6] i2c: i2c-stm32f7: Implement I2C recovery mechanism Pierre-Yves MORDRET
2018-03-24 22:56 ` Wolfram Sang
2018-03-26 8:21 ` Pierre Yves MORDRET
2018-03-24 22:57 ` [PATCH v2 0/6] Add different features for I2C Wolfram Sang
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=fd463a3d-354c-d4e9-16a8-2829ccc04adc@st.com \
--to=pierre-yves.mordret@st.com \
--cc=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=wsa@the-dreams.de \
/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).