Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1548490 > unrolled thread
| Started by | Greentime Hu <green.hu@gmail.com> |
|---|---|
| First post | 2016-12-30 09:10 +0100 |
| Last post | 2017-01-03 14:30 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH v3] net: ethernet: faraday: To support device tree usage. Greentime Hu <green.hu@gmail.com> - 2016-12-30 09:10 +0100
Re: [PATCH v3] net: ethernet: faraday: To support device tree usage. Florian Fainelli <f.fainelli@gmail.com> - 2016-12-31 19:50 +0100
Re: [PATCH v3] net: ethernet: faraday: To support device tree usage. Arnd Bergmann <arnd@arndb.de> - 2016-12-31 21:30 +0100
Re: [PATCH v3] net: ethernet: faraday: To support device tree usage. Arnd Bergmann <arnd@arndb.de> - 2017-01-03 14:30 +0100
| From | Greentime Hu <green.hu@gmail.com> |
|---|---|
| Date | 2016-12-30 09:10 +0100 |
| Subject | [PATCH v3] net: ethernet: faraday: To support device tree usage. |
| Message-ID | <sU0qd-1M6-17@gated-at.bofh.it> |
Signed-off-by: Greentime Hu <green.hu@gmail.com>
---
Changes in v3:
- Nothing changed in this patch but I have committed andestech to vendor-prefixes.txt.
drivers/net/ethernet/faraday/ftmac100.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/net/ethernet/faraday/ftmac100.c b/drivers/net/ethernet/faraday/ftmac100.c
index dce5f7b..5d70ee9 100644
--- a/drivers/net/ethernet/faraday/ftmac100.c
+++ b/drivers/net/ethernet/faraday/ftmac100.c
@@ -1172,11 +1172,17 @@ static int __exit ftmac100_remove(struct platform_device *pdev)
return 0;
}
+static const struct of_device_id ftmac100_of_ids[] = {
+ { .compatible = "andestech,atmac100" },
+ { }
+};
+
static struct platform_driver ftmac100_driver = {
.probe = ftmac100_probe,
.remove = __exit_p(ftmac100_remove),
.driver = {
.name = DRV_NAME,
+ .of_match_table = ftmac100_of_ids
},
};
@@ -1200,3 +1206,4 @@ static void __exit ftmac100_exit(void)
MODULE_AUTHOR("Po-Yu Chuang <ratbert@faraday-tech.com>");
MODULE_DESCRIPTION("FTMAC100 driver");
MODULE_LICENSE("GPL");
+MODULE_DEVICE_TABLE(of, ftmac100_of_ids);
--
1.7.9.5
[toc] | [next] | [standalone]
| From | Florian Fainelli <f.fainelli@gmail.com> |
|---|---|
| Date | 2016-12-31 19:50 +0100 |
| Message-ID | <sUwT7-6ya-7@gated-at.bofh.it> |
| In reply to | #1548490 |
On 12/29/2016 11:37 PM, Greentime Hu wrote: > Signed-off-by: Greentime Hu <green.hu@gmail.com> This is not enough, you need to add a Device Tree binding document under Documentation/devicetree/bindings/net/ which documents this compatible string, as well as additional properties that may be required to describe this hardware block. -- Florian
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-12-31 21:30 +0100 |
| Message-ID | <sUyrY-7EB-5@gated-at.bofh.it> |
| In reply to | #1548821 |
On Saturday, December 31, 2016 10:48:39 AM CET Florian Fainelli wrote: > > On 12/29/2016 11:37 PM, Greentime Hu wrote: > > Signed-off-by: Greentime Hu <green.hu@gmail.com> > > This is not enough, you need to add a Device Tree binding document under > Documentation/devicetree/bindings/net/ which documents this compatible > string, as well as additional properties that may be required to > describe this hardware block. We already have Documentation/devicetree/bindings/net/moxa,moxart-mac.txt for the same hardware (though used by a different driver). I'd suggest renaming that one to a more generic file name and adding the new compatible string there. Aside from that, every patch should also have a changelog comment. Arnd
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2017-01-03 14:30 +0100 |
| Message-ID | <sVxk6-6WU-11@gated-at.bofh.it> |
| In reply to | #1548829 |
On Tuesday, January 3, 2017 2:05:47 PM CET Greentime Hu wrote: > I am not sure if atmac and moxa-art are exactly hardware compatible though > they are based on faraday ftmac. > It may be better if we use 2 different device tree binding documents to > describe for these 2 different drivers to use. They are probably slightly different, but close enough to have the same binding document, as there is no technical reason to have two separate drivers for them. The binding should be about the hardware type, not the way that Linux currently implements the drivers. Arnd
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web