From: Yicong Yang <yangyicong@hisilicon.com>
To: <wsa@kernel.org>, <linux-i2c@vger.kernel.org>
Cc: <andriy.shevchenko@linux.intel.com>, <digetx@gmail.com>,
<treding@nvidia.com>, <jarkko.nikula@linux.intel.com>,
<rmk+kernel@armlinux.org.uk>, <song.bao.hua@hisilicon.com>,
<john.garry@huawei.com>, <yangyicong@hisilicon.com>,
<prime.zeng@huawei.com>, <linuxarm@huawei.com>
Subject: [PATCH v4 0/4] Add support for HiSilicon I2C controller
Date: Tue, 30 Mar 2021 21:05:45 +0800 [thread overview]
Message-ID: <1617109549-4013-1-git-send-email-yangyicong@hisilicon.com> (raw)
Add driver and MAINTAINERS for HiSilicon I2C controller on Kunpeng SoC. Also
provide the devm_*() variants for adding the I2C adapters and a public
api to provide I2C frequency mode strings.
Change since v3:
- split the bus mode string api to I2C as suggested by Andy
- simplify the devm variants and change the export format
- address the comments of the HiSilicon I2C driver from Andy and Dmitry, thanks!
Link: https://lore.kernel.org/linux-i2c/1616411413-7177-1-git-send-email-yangyicong@hisilicon.com/
Change since v2:
- handle -EPROBE_DEFER case when get irq number by platform_get_irq()
Link: https://lore.kernel.org/linux-i2c/1615296137-14558-1-git-send-email-yangyicong@hisilicon.com/
Change since v1:
- fix compile test error on 32bit arch, reported by intel lkp robot:
64 bit division without using kernel wrapper in probe function.
Link:https://lore.kernel.org/linux-i2c/1615016946-55670-1-git-send-email-yangyicong@hisilicon.com/
Yicong Yang (4):
i2c: core: add managed function for adding i2c adapters
i2c: core: add api to provide frequency mode strings
i2c: add support for HiSilicon I2C controller
MAINTAINERS: Add maintainer for HiSilicon I2C driver
MAINTAINERS | 7 +
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-hisi.c | 510 ++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/i2c-core-base.c | 26 +++
include/linux/i2c.h | 21 ++
6 files changed, 575 insertions(+)
create mode 100644 drivers/i2c/busses/i2c-hisi.c
--
2.8.1
next reply other threads:[~2021-03-30 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 13:05 Yicong Yang [this message]
2021-03-30 13:05 ` [PATCH v4 1/4] i2c: core: add managed function for adding i2c adapters Yicong Yang
2021-03-30 13:30 ` Andy Shevchenko
2021-03-30 13:05 ` [PATCH v4 2/4] i2c: core: add api to provide frequency mode strings Yicong Yang
2021-03-30 13:30 ` Andy Shevchenko
2021-03-30 13:05 ` [PATCH v4 3/4] i2c: add support for HiSilicon I2C controller Yicong Yang
2021-03-30 13:29 ` Andy Shevchenko
2021-03-30 13:05 ` [PATCH v4 4/4] MAINTAINERS: Add maintainer for HiSilicon I2C driver Yicong Yang
2021-03-30 13:39 ` [PATCH v4 0/4] Add support for HiSilicon I2C controller Andy Shevchenko
2021-03-30 14:04 ` Yicong Yang
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=1617109549-4013-1-git-send-email-yangyicong@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=digetx@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@huawei.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=song.bao.hua@hisilicon.com \
--cc=treding@nvidia.com \
--cc=wsa@kernel.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).