From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 1/2] i2c: Aspeed: Add AST2600 compatible
Date: Fri, 13 Sep 2019 11:35:09 -0500 [thread overview]
Message-ID: <1568392510-866-2-git-send-email-eajames@linux.ibm.com> (raw)
In-Reply-To: <1568392510-866-1-git-send-email-eajames@linux.ibm.com>
The driver default behavior works with the AST2600. We need a new
compatible though to make sure the driver doesn't enable AST2400 or
AST2500 behavior.
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
drivers/i2c/busses/i2c-aspeed.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/i2c/busses/i2c-aspeed.c b/drivers/i2c/busses/i2c-aspeed.c
index fa66951..c2a6e5a 100644
--- a/drivers/i2c/busses/i2c-aspeed.c
+++ b/drivers/i2c/busses/i2c-aspeed.c
@@ -938,6 +938,10 @@ static int aspeed_i2c_reset(struct aspeed_i2c_bus *bus)
.compatible = "aspeed,ast2500-i2c-bus",
.data = aspeed_i2c_25xx_get_clk_reg_val,
},
+ {
+ .compatible = "aspeed,ast2600-i2c-bus",
+ .data = aspeed_i2c_25xx_get_clk_reg_val,
+ },
{ },
};
MODULE_DEVICE_TABLE(of, aspeed_i2c_bus_of_table);
--
1.8.3.1
WARNING: multiple messages have this Message-ID (diff)
From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org, brendanhiggins@google.com,
joel@jms.id.au, andrew@aj.id.au, robh+dt@kernel.org,
mark.rutland@arm.com, benh@kernel.crashing.org,
Eddie James <eajames@linux.ibm.com>
Subject: [PATCH 1/2] i2c: Aspeed: Add AST2600 compatible
Date: Fri, 13 Sep 2019 11:35:09 -0500 [thread overview]
Message-ID: <1568392510-866-2-git-send-email-eajames@linux.ibm.com> (raw)
In-Reply-To: <1568392510-866-1-git-send-email-eajames@linux.ibm.com>
The driver default behavior works with the AST2600. We need a new
compatible though to make sure the driver doesn't enable AST2400 or
AST2500 behavior.
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
drivers/i2c/busses/i2c-aspeed.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/i2c/busses/i2c-aspeed.c b/drivers/i2c/busses/i2c-aspeed.c
index fa66951..c2a6e5a 100644
--- a/drivers/i2c/busses/i2c-aspeed.c
+++ b/drivers/i2c/busses/i2c-aspeed.c
@@ -938,6 +938,10 @@ static int aspeed_i2c_reset(struct aspeed_i2c_bus *bus)
.compatible = "aspeed,ast2500-i2c-bus",
.data = aspeed_i2c_25xx_get_clk_reg_val,
},
+ {
+ .compatible = "aspeed,ast2600-i2c-bus",
+ .data = aspeed_i2c_25xx_get_clk_reg_val,
+ },
{ },
};
MODULE_DEVICE_TABLE(of, aspeed_i2c_bus_of_table);
--
1.8.3.1
next prev parent reply other threads:[~2019-09-13 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 16:35 [PATCH 0/2] i2c: Aspeed: Add AST2600 compatible string Eddie James
2019-09-13 16:35 ` Eddie James
2019-09-13 16:35 ` Eddie James [this message]
2019-09-13 16:35 ` [PATCH 1/2] i2c: Aspeed: Add AST2600 compatible Eddie James
2019-09-13 16:47 ` Brendan Higgins
2019-09-13 16:47 ` Brendan Higgins
2019-10-21 12:23 ` Wolfram Sang
2019-10-21 12:23 ` Wolfram Sang
2019-09-13 16:35 ` [PATCH 2/2] dt-bindings: " Eddie James
2019-09-13 16:35 ` Eddie James
2019-09-13 16:48 ` Brendan Higgins
2019-09-13 16:48 ` Brendan Higgins
2019-09-30 18:59 ` Rob Herring
2019-09-30 18:59 ` Rob Herring
2019-10-21 12:23 ` Wolfram Sang
2019-10-21 12:23 ` 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=1568392510-866-2-git-send-email-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=linux-aspeed@lists.ozlabs.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 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.