From: Mark Rutland <mark.rutland@arm.com> To: Bjorn Andersson <bjorn.andersson@sonymobile.com> Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>, Ian Campbell <ijc+devicetree@hellion.org.uk>, Kumar Gala <galak@codeaurora.org>, Rob Landley <rob@landley.net>, Wolfram Sang <wsa@the-dreams.de>, "grant.likely@linaro.org" <grant.likely@linaro.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>, "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Andy Gross <agross@codeaurora.org>, Stephen Boyd <sboyd@codeaurora.org>, "Ivan T. Ivanov" <iivanov@mm-sol.com> Subject: Re: [PATCH v3 2/2] i2c: New bus driver for the Qualcomm QUP I2C controller Date: Fri, 21 Feb 2014 11:06:37 +0000 [thread overview] Message-ID: <20140221110637.GG7541@e106331-lin.cambridge.arm.com> (raw) In-Reply-To: <1392943090-30556-3-git-send-email-bjorn.andersson@sonymobile.com> On Fri, Feb 21, 2014 at 12:38:10AM +0000, Bjorn Andersson wrote: > This bus driver supports the QUP i2c hardware controller in the Qualcomm SOCs. > The Qualcomm Universal Peripheral Engine (QUP) is a general purpose data path > engine with input/output FIFOs and an embedded i2c mini-core. The driver > supports FIFO mode (for low bandwidth applications) and block mode (interrupt > generated for each block-size data transfer). > > Cc: Andy Gross <agross@codeaurora.org> > Cc: Stephen Boyd <sboyd@codeaurora.org> > Signed-off-by: Ivan T. Ivanov <iivanov@mm-sol.com> > Signed-off-by: Bjorn Andersson <bjorn.andersson@sonymobile.com> > --- > drivers/i2c/busses/Kconfig | 10 + > drivers/i2c/busses/Makefile | 1 + > drivers/i2c/busses/i2c-qup.c | 772 ++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 783 insertions(+) > create mode 100644 drivers/i2c/busses/i2c-qup.c > > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig > index f5ed031..403e196 100644 > --- a/drivers/i2c/busses/Kconfig > +++ b/drivers/i2c/busses/Kconfig > @@ -648,6 +648,16 @@ config I2C_PXA_SLAVE > is necessary for systems where the PXA may be a target on the > I2C bus. [...] > +static const struct of_device_id qup_i2c_dt_match[] = { > + { .compatible = "qcom,i2c-qup-v1.1.1" }, > + { .compatible = "qcom,i2c-qup-v2.1.1" }, > + { .compatible = "qcom,i2c-qup-v2.2.1" }, The all seem to be handled the same. Are they all compatible with the "qcom,i2c-qup-v1.1.1" programming model, such that it could be used as a fallback in the compatible list (and the driver would only need to look for it for now)? Cheers, Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 2/2] i2c: New bus driver for the Qualcomm QUP I2C controller Date: Fri, 21 Feb 2014 11:06:37 +0000 [thread overview] Message-ID: <20140221110637.GG7541@e106331-lin.cambridge.arm.com> (raw) In-Reply-To: <1392943090-30556-3-git-send-email-bjorn.andersson@sonymobile.com> On Fri, Feb 21, 2014 at 12:38:10AM +0000, Bjorn Andersson wrote: > This bus driver supports the QUP i2c hardware controller in the Qualcomm SOCs. > The Qualcomm Universal Peripheral Engine (QUP) is a general purpose data path > engine with input/output FIFOs and an embedded i2c mini-core. The driver > supports FIFO mode (for low bandwidth applications) and block mode (interrupt > generated for each block-size data transfer). > > Cc: Andy Gross <agross@codeaurora.org> > Cc: Stephen Boyd <sboyd@codeaurora.org> > Signed-off-by: Ivan T. Ivanov <iivanov@mm-sol.com> > Signed-off-by: Bjorn Andersson <bjorn.andersson@sonymobile.com> > --- > drivers/i2c/busses/Kconfig | 10 + > drivers/i2c/busses/Makefile | 1 + > drivers/i2c/busses/i2c-qup.c | 772 ++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 783 insertions(+) > create mode 100644 drivers/i2c/busses/i2c-qup.c > > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig > index f5ed031..403e196 100644 > --- a/drivers/i2c/busses/Kconfig > +++ b/drivers/i2c/busses/Kconfig > @@ -648,6 +648,16 @@ config I2C_PXA_SLAVE > is necessary for systems where the PXA may be a target on the > I2C bus. [...] > +static const struct of_device_id qup_i2c_dt_match[] = { > + { .compatible = "qcom,i2c-qup-v1.1.1" }, > + { .compatible = "qcom,i2c-qup-v2.1.1" }, > + { .compatible = "qcom,i2c-qup-v2.2.1" }, The all seem to be handled the same. Are they all compatible with the "qcom,i2c-qup-v1.1.1" programming model, such that it could be used as a fallback in the compatible list (and the driver would only need to look for it for now)? Cheers, Mark.
next prev parent reply other threads:[~2014-02-21 11:06 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-21 0:38 [PATCH v3 0/2] Qualcomm Universal Peripheral (QUP) I2C controller Bjorn Andersson 2014-02-21 0:38 ` Bjorn Andersson 2014-02-21 0:38 ` Bjorn Andersson [not found] ` <1392943090-30556-1-git-send-email-bjorn.andersson-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org> 2014-02-21 0:38 ` [PATCH v3 1/2] i2c: qup: Add device tree bindings information Bjorn Andersson 2014-02-21 0:38 ` Bjorn Andersson 2014-02-21 0:38 ` Bjorn Andersson 2014-02-21 11:01 ` Mark Rutland 2014-02-21 11:01 ` Mark Rutland 2014-02-21 11:01 ` Mark Rutland 2014-02-21 0:38 ` [PATCH v3 2/2] i2c: New bus driver for the Qualcomm QUP I2C controller Bjorn Andersson 2014-02-21 0:38 ` Bjorn Andersson 2014-02-21 0:38 ` Bjorn Andersson 2014-02-21 0:52 ` Joe Perches 2014-02-21 0:52 ` Joe Perches 2014-02-24 17:51 ` Bjorn Andersson 2014-02-24 17:51 ` Bjorn Andersson 2014-02-24 17:51 ` Bjorn Andersson 2014-02-21 2:53 ` Emilio López 2014-02-21 2:53 ` Emilio López 2014-02-24 18:00 ` Bjorn Andersson 2014-02-24 18:00 ` Bjorn Andersson 2014-02-24 18:00 ` Bjorn Andersson 2014-02-21 8:16 ` Maxime Ripard 2014-02-21 8:16 ` Maxime Ripard 2014-02-21 8:16 ` Maxime Ripard 2014-02-24 18:03 ` Bjorn Andersson 2014-02-24 18:03 ` Bjorn Andersson 2014-02-24 18:03 ` Bjorn Andersson 2014-02-21 11:06 ` Mark Rutland [this message] 2014-02-21 11:06 ` Mark Rutland 2014-02-21 11:06 ` Mark Rutland 2014-02-25 16:07 ` Bjorn Andersson 2014-02-25 16:07 ` Bjorn Andersson 2014-02-25 16:07 ` Bjorn Andersson 2014-02-25 16:56 ` Andy Gross 2014-02-25 16:56 ` Andy Gross 2014-02-25 16:56 ` Andy Gross [not found] ` <1392943090-30556-3-git-send-email-bjorn.andersson-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org> 2014-02-21 15:35 ` Kumar Gala 2014-02-21 15:35 ` Kumar Gala 2014-02-21 15:35 ` Kumar Gala 2014-02-24 10:33 ` Ivan T. Ivanov 2014-02-24 10:33 ` Ivan T. Ivanov 2014-02-24 17:40 ` Josh Cartwright 2014-02-24 17:40 ` Josh Cartwright 2014-02-24 18:05 ` Bjorn Andersson 2014-02-24 18:05 ` Bjorn Andersson 2014-02-24 18:05 ` Bjorn Andersson 2014-03-05 16:44 ` Wolfram Sang 2014-03-05 16:44 ` 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=20140221110637.GG7541@e106331-lin.cambridge.arm.com \ --to=mark.rutland@arm.com \ --cc=Pawel.Moll@arm.com \ --cc=agross@codeaurora.org \ --cc=bjorn.andersson@sonymobile.com \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=grant.likely@linaro.org \ --cc=iivanov@mm-sol.com \ --cc=ijc+devicetree@hellion.org.uk \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-i2c@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rob@landley.net \ --cc=robh+dt@kernel.org \ --cc=sboyd@codeaurora.org \ --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: linkBe 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.