From: Joseph CHANG <josright123@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Joseph CHANG <josright123@gmail.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] *** ADD DM9051 NET DEVICE ***
Date: Fri, 3 Dec 2021 04:46:54 +0800 [thread overview]
Message-ID: <20211202204656.4411-1-josright123@gmail.com> (raw)
*** DM9051 is a SPI interface ethernet controller chip ***
*** For a embedded Linux device to construct an ethernet port ***
*** Fewer CPU interface pins is its advantage comapre to DM9000 ***
*** It need only cs / mosi / miso / clock and an interrupt pin ***
Joseph CHANG (2):
yaml: Add dm9051 SPI network yaml file
net: Add DM9051 driver
.../bindings/net/davicom,dm9051.yaml | 62 ++
drivers/net/ethernet/davicom/Kconfig | 30 +
drivers/net/ethernet/davicom/Makefile | 1 +
drivers/net/ethernet/davicom/dm9051.c | 987 ++++++++++++++++++
drivers/net/ethernet/davicom/dm9051.h | 259 +++++
5 files changed, 1339 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/davicom,dm9051.yaml
create mode 100644 drivers/net/ethernet/davicom/dm9051.c
create mode 100644 drivers/net/ethernet/davicom/dm9051.h
base-commit: ce83278f313ce65a9bbd780a3e07fa3f62d82525
--
2.25.1
next reply other threads:[~2021-12-08 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 20:46 Joseph CHANG [this message]
2021-12-02 20:46 ` [PATCH 1/2] yaml: Add dm9051 SPI network yaml file Joseph CHANG
2021-12-08 13:44 ` Rob Herring
2021-12-02 20:46 ` [PATCH 2/2] net: Add DM9051 driver Joseph CHANG
2021-12-08 14:41 ` kernel test robot
2021-12-08 21:09 ` kernel test robot
2021-12-09 2:08 ` Andrew Lunn
2021-12-08 21:39 ` [PATCH 0/2] *** ADD DM9051 NET DEVICE *** Jakub Kicinski
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=20211202204656.4411-1-josright123@gmail.com \
--to=josright123@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).