linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Rosin <peda@axentia.se>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PULL REQUEST] i2c for 5.10
Date: Sat, 5 Dec 2020 23:11:43 +0100	[thread overview]
Message-ID: <20201205221143.GA19137@kunai> (raw)

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

Linus,

here are some more I2C driver updates. IMX updates are a tad bigger, but
not exceptionally big.

Please pull.

Thanks,

   Wolfram


The following changes since commit b65054597872ce3aefbc6a666385eabdf9e288da:

  Linux 5.10-rc6 (2020-11-29 15:50:50 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current

for you to fetch changes up to 2bf9545626f8d09f552ab86d0047a415fe9a07a0:

  i2c: mlxbf: Fix the return check of devm_ioremap and ioremap (2020-12-05 14:52:35 +0100)

----------------------------------------------------------------
Arnd Bergmann (1):
      i2c: mlxbf: select CONFIG_I2C_SLAVE

Christian Eggers (3):
      i2c: imx: Fix reset of I2SR_IAL flag
      i2c: imx: Check for I2SR_IAL after every byte
      i2c: imx: Don't generate STOP condition if arbitration has been lost

Robert Foss (1):
      i2c: qcom: Fix IRQ error misassignement

Wang Xiaojun (1):
      i2c: mlxbf: Fix the return check of devm_ioremap and ioremap

Zhihao Cheng (1):
      i2c: qup: Fix error return code in qup_i2c_bam_schedule_desc()


with much appreciated quality assurance from
----------------------------------------------------------------
Bjorn Andersson (1):
      (Rev.) i2c: qup: Fix error return code in qup_i2c_bam_schedule_desc()

Krzysztof Kozlowski (2):
      (Test) i2c: imx: Don't generate STOP condition if arbitration has been lost
      (Test) i2c: imx: Check for I2SR_IAL after every byte

Manivannan Sadhasivam (1):
      (Rev.) i2c: qcom: Fix IRQ error misassignement

Uwe Kleine-König (1):
      (Rev.) i2c: imx: Fix reset of I2SR_IAL flag

 drivers/i2c/busses/Kconfig        |  1 +
 drivers/i2c/busses/i2c-imx.c      | 44 ++++++++++++++++++++++++++++++++-------
 drivers/i2c/busses/i2c-mlxbf.c    | 12 +++++------
 drivers/i2c/busses/i2c-qcom-cci.c |  4 ++--
 drivers/i2c/busses/i2c-qup.c      |  3 ++-
 5 files changed, 47 insertions(+), 17 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-12-05 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 22:11 Wolfram Sang [this message]
2020-12-05 23:33 ` [PULL REQUEST] i2c for 5.10 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-12-12 18:30 Wolfram Sang
2020-12-12 21:03 ` pr-tracker-bot
2020-11-07 18:39 Wolfram Sang
2020-11-07 19:43 ` pr-tracker-bot
2020-10-25 12:37 Wolfram Sang
2020-10-25 18:35 ` pr-tracker-bot
2020-10-21  6:55 Wolfram Sang
2020-10-21 18:35 ` pr-tracker-bot

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=20201205221143.GA19137@kunai \
    --to=wsa@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=torvalds@linux-foundation.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).