From: Vinod Koul <vkoul@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Todor Tomov <todor.tomov@linaro.org>,
Vinod Koul <vkoul@kernel.org>
Subject: [PATCH v4 0/2] i2c: Add support for Qcom CCI I2C controller
Date: Mon, 20 Aug 2018 12:09:51 +0530 [thread overview]
Message-ID: <20180820063953.6866-1-vkoul@kernel.org> (raw)
Hi,
This series adds support for Qualcomm Camera Control Interface (CCI) I2C
controller. This block contains one/two I2C masters and registers these
adapters based on the controller probed on.
Changes in v4:
- Add pm support
- Fix based on Bjorn feedback
Changes in v3:
- Update DT binding per RobH comments
- Add the subnode for bus instances
- Move all compataible data to driver data
- add num_master data and use that to register and use masters
Changes in v2:
- Add support for two adapters
Todor Tomov (2):
dt-bindings: i2c: Add binding for Qualcomm CCI I2C controller
i2c: Add Qualcomm CCI I2C driver
.../devicetree/bindings/i2c/i2c-qcom-cci.txt | 83 ++
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-qcom-cci.c | 879 +++++++++++++++++++++
4 files changed, 973 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-qcom-cci.txt
create mode 100644 drivers/i2c/busses/i2c-qcom-cci.c
--
2.14.4
next reply other threads:[~2018-08-20 6:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 6:39 Vinod Koul [this message]
2018-08-20 6:39 ` [PATCH v4 1/2] dt-bindings: i2c: Add binding for Qualcomm CCI I2C controller Vinod Koul
2018-08-20 18:18 ` Rob Herring
2018-08-21 9:28 ` Vinod
2018-08-21 13:11 ` Rob Herring
2018-08-21 13:12 ` Rob Herring
2018-08-21 16:00 ` Vinod
2018-08-20 6:39 ` [PATCH v4 2/2] i2c: Add Qualcomm CCI I2C driver Vinod Koul
2018-08-24 7:30 ` Stephen Boyd
2018-08-24 10:16 ` Vinod
2018-08-27 19:19 ` Stephen Boyd
2018-08-28 3:38 ` Vinod
2018-09-20 19:39 ` Ricardo Ribalda Delgado
2018-09-21 15:36 ` Vinod
2018-09-21 15:43 ` Todor Tomov
2018-09-22 22:02 ` Ricardo Ribalda Delgado
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=20180820063953.6866-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=todor.tomov@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.