linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/5] i2c: Add STM32F4 I2C driver
Date: Sun, 11 Dec 2016 22:42:33 +0100	[thread overview]
Message-ID: <20161211214232.GA2552@katana> (raw)
In-Reply-To: <1481185563-8735-3-git-send-email-cedric.madianga@gmail.com>

Hi,

> +config I2C_STM32F4
> +	tristate "STMicroelectronics STM32F4 I2C support"
> +	depends on ARCH_STM32  || COMPILE_TEST

Double space.

> +#define STM32F4_I2C_MIN_FREQ		2
> +#define STM32F4_I2C_MAX_FREQ		42

Those two must be unsigned to fix the build error (e.g. 2U) reported by
build-bot.

Also, I get the following build warnings:

  CC      drivers/i2c/busses/i2c-stm32f4.o
drivers/i2c/busses/i2c-stm32f4.c: In function ?stm32f4_i2c_handle_rx_addr?:
drivers/i2c/busses/i2c-stm32f4.c:445:6: warning: variable ?sr2? set but not used [-Wunused-but-set-variable]
  u32 sr2;
      ^~~
drivers/i2c/busses/i2c-stm32f4.c: In function ?stm32f4_i2c_isr_event?:
drivers/i2c/busses/i2c-stm32f4.c:496:41: warning: variable ?sr2? set but not used [-Wunused-but-set-variable]
  u32 real_status, possible_status, ien, sr2;

I assume those are reads to clear the register, so we really don't need
to save the value in a variable.

Rest is looking good.

Thanks,

   Wolfram

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161211/0379cc61/attachment.sig>

  parent reply	other threads:[~2016-12-11 21:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  8:25 [PATCH v5 0/5] Add support for the STM32F4 I2C M'boumba Cedric Madianga
2016-12-08  8:25 ` [PATCH v5 1/5] dt-bindings: Document the STM32 I2C bindings M'boumba Cedric Madianga
2016-12-08  8:26 ` [PATCH v5 2/5] i2c: Add STM32F4 I2C driver M'boumba Cedric Madianga
2016-12-08 10:47   ` kbuild test robot
2016-12-08 11:42   ` kbuild test robot
2016-12-08 12:18   ` kbuild test robot
2016-12-11 21:42   ` Wolfram Sang [this message]
2016-12-12  8:34     ` M'boumba Cedric Madianga
2016-12-08  8:26 ` [PATCH v5 3/5] ARM: dts: Add I2C1 support for STM32F429 SoC M'boumba Cedric Madianga
2016-12-08  8:26 ` [PATCH v5 4/5] ARM: dts: Add I2C1 support for STM32429 eval board M'boumba Cedric Madianga
2016-12-08  8:39   ` Alexandre Torgue
2016-12-08  8:47     ` M'boumba Cedric Madianga
2016-12-08  8:26 ` [PATCH v5 5/5] ARM: configs: Add I2C support for STM32 defconfig M'boumba Cedric Madianga
2016-12-08  8:38   ` Alexandre Torgue
2016-12-08  8:47     ` M'boumba Cedric Madianga

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=20161211214232.GA2552@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).