From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
To: Wolfram Sang <wsa@the-dreams.de>, linux-i2c@vger.kernel.org
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Eddie Huang <eddie.huang@mediatek.com>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks
Date: Fri, 13 Mar 2015 14:20:11 +0530 [thread overview]
Message-ID: <5502A4C3.2040004@linux.vnet.ibm.com> (raw)
In-Reply-To: <1424880126-15047-5-git-send-email-wsa@the-dreams.de>
[-- Attachment #1.1: Type: text/plain, Size: 3890 bytes --]
Hi Wolfram,
Based on your patch:
"[RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks"
From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
Subject: [PATCH] i2c: opal: Update quirk flags to do write-then-anything
Support write-then-anything in the case of 2 i2c messages
for i2c transfer.
Signed-off-by: Neelesh Gupta<neelegup@linux.vnet.ibm.com>
---
drivers/i2c/busses/i2c-opal.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/i2c/busses/i2c-opal.c b/drivers/i2c/busses/i2c-opal.c
index b2788ec..1ec7fc9 100644
--- a/drivers/i2c/busses/i2c-opal.c
+++ b/drivers/i2c/busses/i2c-opal.c
@@ -104,7 +104,8 @@ static int i2c_opal_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
req.buffer_ra = cpu_to_be64(__pa(msgs[0].buf));
break;
case 2:
- req.type = OPAL_I2C_SM_READ;
+ req.type = (msgs[1].flags & I2C_M_RD) ?
+ OPAL_I2C_SM_READ : OPAL_I2C_SM_WRITE;
req.addr = cpu_to_be16(msgs[0].addr);
req.subaddr_sz = msgs[0].len;
for (i = 0; i < msgs[0].len; i++)
@@ -199,13 +200,11 @@ static const struct i2c_algorithm i2c_opal_algo = {
.functionality = i2c_opal_func,
};
-/* For two messages, we basically support only simple
- * smbus transactions of a write plus a read. We might
- * want to allow also two writes but we'd have to bounce
- * the data into a single buffer.
+/* For two messages, we basically support simple smbus transactions of a
+ * write-then-anything.
*/
static struct i2c_adapter_quirks i2c_opal_quirks = {
- .flags = I2C_AQ_COMB_WRITE_THEN_READ,
+ .flags = I2C_AQ_COMB | I2C_AQ_COMB_WRITE_FIRST | I2C_AQ_COMB_SAME_ADDR,
.max_comb_1st_msg_len = 4,
};
On 02/25/2015 09:31 PM, Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> drivers/i2c/busses/i2c-opal.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-opal.c b/drivers/i2c/busses/i2c-opal.c
> index 16f90b1a750894..b2788ecad5b3cb 100644
> --- a/drivers/i2c/busses/i2c-opal.c
> +++ b/drivers/i2c/busses/i2c-opal.c
> @@ -104,17 +104,6 @@ static int i2c_opal_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
> req.buffer_ra = cpu_to_be64(__pa(msgs[0].buf));
> break;
> case 2:
> - /* For two messages, we basically support only simple
> - * smbus transactions of a write plus a read. We might
> - * want to allow also two writes but we'd have to bounce
> - * the data into a single buffer.
> - */
> - if ((msgs[0].flags & I2C_M_RD) || !(msgs[1].flags & I2C_M_RD))
> - return -EOPNOTSUPP;
> - if (msgs[0].len > 4)
> - return -EOPNOTSUPP;
> - if (msgs[0].addr != msgs[1].addr)
> - return -EOPNOTSUPP;
> req.type = OPAL_I2C_SM_READ;
> req.addr = cpu_to_be16(msgs[0].addr);
> req.subaddr_sz = msgs[0].len;
> @@ -210,6 +199,16 @@ static const struct i2c_algorithm i2c_opal_algo = {
> .functionality = i2c_opal_func,
> };
>
> +/* For two messages, we basically support only simple
> + * smbus transactions of a write plus a read. We might
> + * want to allow also two writes but we'd have to bounce
> + * the data into a single buffer.
> + */
> +static struct i2c_adapter_quirks i2c_opal_quirks = {
> + .flags = I2C_AQ_COMB_WRITE_THEN_READ,
> + .max_comb_1st_msg_len = 4,
> +};
> +
> static int i2c_opal_probe(struct platform_device *pdev)
> {
> struct i2c_adapter *adapter;
> @@ -232,6 +231,7 @@ static int i2c_opal_probe(struct platform_device *pdev)
>
> adapter->algo = &i2c_opal_algo;
> adapter->algo_data = (void *)(unsigned long)opal_id;
> + adapter->quirks = &i2c_opal_quirks;
> adapter->dev.parent = &pdev->dev;
> adapter->dev.of_node = of_node_get(pdev->dev.of_node);
> pname = of_get_property(pdev->dev.of_node, "ibm,port-name", NULL);
[-- Attachment #1.2: Type: text/html, Size: 4796 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
WARNING: multiple messages have this Message-ID (diff)
From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
To: Wolfram Sang <wsa@the-dreams.de>, linux-i2c@vger.kernel.org
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Eddie Huang <eddie.huang@mediatek.com>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks
Date: Fri, 13 Mar 2015 14:20:11 +0530 [thread overview]
Message-ID: <5502A4C3.2040004@linux.vnet.ibm.com> (raw)
In-Reply-To: <1424880126-15047-5-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 3890 bytes --]
Hi Wolfram,
Based on your patch:
"[RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks"
From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
Subject: [PATCH] i2c: opal: Update quirk flags to do write-then-anything
Support write-then-anything in the case of 2 i2c messages
for i2c transfer.
Signed-off-by: Neelesh Gupta<neelegup@linux.vnet.ibm.com>
---
drivers/i2c/busses/i2c-opal.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/i2c/busses/i2c-opal.c b/drivers/i2c/busses/i2c-opal.c
index b2788ec..1ec7fc9 100644
--- a/drivers/i2c/busses/i2c-opal.c
+++ b/drivers/i2c/busses/i2c-opal.c
@@ -104,7 +104,8 @@ static int i2c_opal_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
req.buffer_ra = cpu_to_be64(__pa(msgs[0].buf));
break;
case 2:
- req.type = OPAL_I2C_SM_READ;
+ req.type = (msgs[1].flags & I2C_M_RD) ?
+ OPAL_I2C_SM_READ : OPAL_I2C_SM_WRITE;
req.addr = cpu_to_be16(msgs[0].addr);
req.subaddr_sz = msgs[0].len;
for (i = 0; i < msgs[0].len; i++)
@@ -199,13 +200,11 @@ static const struct i2c_algorithm i2c_opal_algo = {
.functionality = i2c_opal_func,
};
-/* For two messages, we basically support only simple
- * smbus transactions of a write plus a read. We might
- * want to allow also two writes but we'd have to bounce
- * the data into a single buffer.
+/* For two messages, we basically support simple smbus transactions of a
+ * write-then-anything.
*/
static struct i2c_adapter_quirks i2c_opal_quirks = {
- .flags = I2C_AQ_COMB_WRITE_THEN_READ,
+ .flags = I2C_AQ_COMB | I2C_AQ_COMB_WRITE_FIRST | I2C_AQ_COMB_SAME_ADDR,
.max_comb_1st_msg_len = 4,
};
On 02/25/2015 09:31 PM, Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> drivers/i2c/busses/i2c-opal.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-opal.c b/drivers/i2c/busses/i2c-opal.c
> index 16f90b1a750894..b2788ecad5b3cb 100644
> --- a/drivers/i2c/busses/i2c-opal.c
> +++ b/drivers/i2c/busses/i2c-opal.c
> @@ -104,17 +104,6 @@ static int i2c_opal_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
> req.buffer_ra = cpu_to_be64(__pa(msgs[0].buf));
> break;
> case 2:
> - /* For two messages, we basically support only simple
> - * smbus transactions of a write plus a read. We might
> - * want to allow also two writes but we'd have to bounce
> - * the data into a single buffer.
> - */
> - if ((msgs[0].flags & I2C_M_RD) || !(msgs[1].flags & I2C_M_RD))
> - return -EOPNOTSUPP;
> - if (msgs[0].len > 4)
> - return -EOPNOTSUPP;
> - if (msgs[0].addr != msgs[1].addr)
> - return -EOPNOTSUPP;
> req.type = OPAL_I2C_SM_READ;
> req.addr = cpu_to_be16(msgs[0].addr);
> req.subaddr_sz = msgs[0].len;
> @@ -210,6 +199,16 @@ static const struct i2c_algorithm i2c_opal_algo = {
> .functionality = i2c_opal_func,
> };
>
> +/* For two messages, we basically support only simple
> + * smbus transactions of a write plus a read. We might
> + * want to allow also two writes but we'd have to bounce
> + * the data into a single buffer.
> + */
> +static struct i2c_adapter_quirks i2c_opal_quirks = {
> + .flags = I2C_AQ_COMB_WRITE_THEN_READ,
> + .max_comb_1st_msg_len = 4,
> +};
> +
> static int i2c_opal_probe(struct platform_device *pdev)
> {
> struct i2c_adapter *adapter;
> @@ -232,6 +231,7 @@ static int i2c_opal_probe(struct platform_device *pdev)
>
> adapter->algo = &i2c_opal_algo;
> adapter->algo_data = (void *)(unsigned long)opal_id;
> + adapter->quirks = &i2c_opal_quirks;
> adapter->dev.parent = &pdev->dev;
> adapter->dev.of_node = of_node_get(pdev->dev.of_node);
> pname = of_get_property(pdev->dev.of_node, "ibm,port-name", NULL);
[-- Attachment #2: Type: text/html, Size: 4796 bytes --]
next prev parent reply other threads:[~2015-03-13 8:50 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 16:01 [RFC V2 00/12] i2c: describe adapter quirks in a generic way Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 01/12] i2c: add quirk structure to describe adapter flaws Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
[not found] ` <1424880126-15047-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-02-25 16:01 ` [RFC V2 02/12] i2c: add quirk checks to core Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
[not found] ` <1424880126-15047-4-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-03-08 8:28 ` Wolfram Sang
2015-03-08 8:28 ` Wolfram Sang
2015-03-08 8:28 ` Wolfram Sang
2015-03-08 8:28 ` Wolfram Sang
2015-03-09 16:11 ` Ludovic Desroches
2015-03-09 16:11 ` Ludovic Desroches
2015-03-09 16:11 ` Ludovic Desroches
2015-03-09 16:11 ` Ludovic Desroches
2015-03-09 16:11 ` Ludovic Desroches
2015-03-10 13:55 ` Ludovic Desroches
2015-03-10 13:55 ` Ludovic Desroches
2015-03-10 13:55 ` Ludovic Desroches
2015-03-10 13:55 ` Ludovic Desroches
2015-03-12 14:50 ` Wolfram Sang
2015-03-12 14:50 ` Wolfram Sang
2015-03-05 13:27 ` [RFC V2 00/12] i2c: describe adapter quirks in a generic way Ivan T. Ivanov
2015-03-05 13:27 ` Ivan T. Ivanov
2015-03-05 13:27 ` Ivan T. Ivanov
2015-03-05 13:27 ` Ivan T. Ivanov
2015-03-12 14:56 ` Wolfram Sang
2015-03-12 14:56 ` Wolfram Sang
2015-03-12 14:56 ` Wolfram Sang
2015-03-14 11:14 ` Wolfram Sang
2015-03-14 11:14 ` Wolfram Sang
2015-03-14 11:14 ` Wolfram Sang
2015-03-14 11:14 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
[not found] ` <1424880126-15047-5-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-03-10 17:13 ` Neelesh Gupta
2015-03-10 17:13 ` Neelesh Gupta
2015-03-10 17:13 ` Neelesh Gupta
2015-03-10 17:13 ` Neelesh Gupta
2015-03-10 23:12 ` Benjamin Herrenschmidt
2015-03-10 23:12 ` Benjamin Herrenschmidt
2015-03-10 23:12 ` Benjamin Herrenschmidt
[not found] ` <1426029133.17565.9.camel-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2015-03-11 4:26 ` Neelesh Gupta
2015-03-11 4:26 ` Neelesh Gupta
2015-03-11 4:26 ` Neelesh Gupta
2015-03-11 4:26 ` Neelesh Gupta
2015-03-12 14:55 ` Wolfram Sang
2015-03-12 14:55 ` Wolfram Sang
2015-03-12 14:55 ` Wolfram Sang
2015-03-13 8:50 ` Neelesh Gupta [this message]
2015-03-13 8:50 ` Neelesh Gupta
2015-02-25 16:01 ` [RFC V2 05/12] i2c: qup: " Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 06/12] i2c: cpm: " Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 07/12] i2c: axxia: " Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 08/12] i2c: dln2: " Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:01 ` Wolfram Sang
2015-02-25 16:02 ` [RFC V2 09/12] i2c: powermac: " Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` [RFC V2 10/12] i2c: viperboard: " Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` [RFC V2 11/12] i2c: pmcmsp: " Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` [RFC V2 12/12] i2c: bcm-iproc: " Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-25 16:02 ` Wolfram Sang
2015-02-26 23:32 ` Ray Jui
2015-02-26 23:32 ` Ray Jui
2015-02-26 23:32 ` Ray Jui
2015-02-26 23:32 ` Ray Jui
2015-03-12 14:56 ` Wolfram Sang
2015-03-12 14:56 ` Wolfram Sang
2015-03-12 14:56 ` 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=5502A4C3.2040004@linux.vnet.ibm.com \
--to=neelegup@linux.vnet.ibm.com \
--cc=eddie.huang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ludovic.desroches@atmel.com \
--cc=wsa@the-dreams.de \
--cc=yingjoe.chen@mediatek.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.