From: <Parthiban.Veerasooran@microchip.com>
To: <rdunlap@infradead.org>
Cc: <masahiroy@kernel.org>, <alexanderduyck@fb.com>,
<krzk+dt@kernel.org>, <robh@kernel.org>, <hkallweit1@gmail.com>,
<linux@armlinux.org.uk>, <UNGLinuxDriver@microchip.com>,
<Thorsten.Kummermehr@microchip.com>, <Pier.Beruto@onsemi.com>,
<Selvamani.Rajagopal@onsemi.com>, <Nicolas.Ferre@microchip.com>,
<benjamin.bigler@bernformulastudent.ch>, <linux@bigler.io>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <horms@kernel.org>, <saeedm@nvidia.com>,
<anthony.l.nguyen@intel.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <andrew@lunn.ch>,
<corbet@lwn.net>, <linux-doc@vger.kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<Horatiu.Vultur@microchip.com>, <ruanjinjie@huawei.com>,
<Steen.Hegelund@microchip.com>, <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next v5 13/14] microchip: lan865x: add driver support for Microchip's LAN865X MAC-PHY
Date: Wed, 31 Jul 2024 07:55:34 +0000 [thread overview]
Message-ID: <6acd6d65-7dfb-4b3d-9a39-edcc5728261f@microchip.com> (raw)
In-Reply-To: <6750b19d-4af3-44c8-90a6-9cb70fcec385@infradead.org>
Hi Randy,
On 30/07/24 9:45 am, Randy Dunlap wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 7/29/24 9:09 PM, Parthiban Veerasooran wrote:
>> The LAN8650/1 is designed to conform to the OPEN Alliance 10BASE-T1x
>> MAC-PHY Serial Interface specification, Version 1.1. The IEEE Clause 4
>> MAC integration provides the low pin count standard SPI interface to any
>> microcontroller therefore providing Ethernet functionality without
>> requiring MAC integration within the microcontroller. The LAN8650/1
>> operates as an SPI client supporting SCLK clock rates up to a maximum of
>> 25 MHz. This SPI interface supports the transfer of both data (Ethernet
>> frames) and control (register access).
>>
>> By default, the chunk data payload is 64 bytes in size. The Ethernet
>> Media Access Controller (MAC) module implements a 10 Mbps half duplex
>> Ethernet MAC, compatible with the IEEE 802.3 standard. 10BASE-T1S
>> physical layer transceiver integrated is into the LAN8650/1. The PHY and
>> MAC are connected via an internal Media Independent Interface (MII).
>>
>> Signed-off-by: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
>> ---
>> MAINTAINERS | 6 +
>> drivers/net/ethernet/microchip/Kconfig | 1 +
>> drivers/net/ethernet/microchip/Makefile | 1 +
>> .../net/ethernet/microchip/lan865x/Kconfig | 19 +
>> .../net/ethernet/microchip/lan865x/Makefile | 6 +
>> .../net/ethernet/microchip/lan865x/lan865x.c | 391 ++++++++++++++++++
>> 6 files changed, 424 insertions(+)
>> create mode 100644 drivers/net/ethernet/microchip/lan865x/Kconfig
>> create mode 100644 drivers/net/ethernet/microchip/lan865x/Makefile
>> create mode 100644 drivers/net/ethernet/microchip/lan865x/lan865x.c
>>
>
>> diff --git a/drivers/net/ethernet/microchip/lan865x/Kconfig b/drivers/net/ethernet/microchip/lan865x/Kconfig
>> new file mode 100644
>> index 000000000000..f3d60d14e202
>> --- /dev/null
>> +++ b/drivers/net/ethernet/microchip/lan865x/Kconfig
>> @@ -0,0 +1,19 @@
>> +# SPDX-License-Identifier: GPL-2.0-only
>> +#
>> +# Microchip LAN865x Driver Support
>> +#
>> +
>> +if NET_VENDOR_MICROCHIP
>> +
>> +config LAN865X
>> + tristate "LAN865x support"
>> + depends on SPI
>> + depends on OA_TC6
>
> Since OA_TC6 is described as a library, it would make sense to select OA_TC6 here instead
> of depending on it.
> OTOH, that might cause some Kconfig dependency issues... I haven't looked into that.Yes that makes sense. I will change it in the next version.
Best regards,
Parthiban V
>
>> + help
>> + Support for the Microchip LAN8650/1 Rev.B1 MACPHY Ethernet chip. It
>> + uses OPEN Alliance 10BASE-T1x Serial Interface specification.
>> +
>> + To compile this driver as a module, choose M here. The module will be
>> + called lan865x.
>> +
>> +endif # NET_VENDOR_MICROCHIP
>
>
> --
> ~Randy
next prev parent reply other threads:[~2024-07-31 7:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 4:08 [PATCH net-next v5 00/14] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface Parthiban Veerasooran
2024-07-30 4:08 ` [PATCH net-next v5 01/14] Documentation: networking: add OPEN Alliance 10BASE-T1x MAC-PHY serial interface Parthiban Veerasooran
2024-08-11 15:35 ` Andrew Lunn
2024-07-30 4:08 ` [PATCH net-next v5 02/14] net: ethernet: oa_tc6: implement register write operation Parthiban Veerasooran
2024-07-30 4:08 ` [PATCH net-next v5 03/14] net: ethernet: oa_tc6: implement register read operation Parthiban Veerasooran
2024-08-11 15:37 ` Andrew Lunn
2024-07-30 4:08 ` [PATCH net-next v5 04/14] net: ethernet: oa_tc6: implement software reset Parthiban Veerasooran
2024-08-11 15:39 ` Andrew Lunn
2024-07-30 4:08 ` [PATCH net-next v5 05/14] net: ethernet: oa_tc6: implement error interrupts unmasking Parthiban Veerasooran
2024-07-30 4:08 ` [PATCH net-next v5 06/14] net: ethernet: oa_tc6: implement internal PHY initialization Parthiban Veerasooran
2024-08-11 15:47 ` Andrew Lunn
2024-07-30 4:08 ` [PATCH net-next v5 07/14] net: phy: microchip_t1s: add c45 direct access in LAN865x internal PHY Parthiban Veerasooran
2024-08-11 15:48 ` Andrew Lunn
2024-07-30 4:09 ` [PATCH net-next v5 08/14] net: ethernet: oa_tc6: enable open alliance tc6 data communication Parthiban Veerasooran
2024-07-30 4:09 ` [PATCH net-next v5 09/14] net: ethernet: oa_tc6: implement transmit path to transfer tx ethernet frames Parthiban Veerasooran
2024-08-11 15:54 ` Andrew Lunn
2024-07-30 4:09 ` [PATCH net-next v5 10/14] net: ethernet: oa_tc6: implement receive path to receive rx " Parthiban Veerasooran
2024-08-11 15:56 ` Andrew Lunn
2024-07-30 4:09 ` [PATCH net-next v5 11/14] net: ethernet: oa_tc6: implement mac-phy interrupt Parthiban Veerasooran
2024-07-30 4:09 ` [PATCH net-next v5 12/14] net: ethernet: oa_tc6: add helper function to enable zero align rx frame Parthiban Veerasooran
2024-08-11 15:57 ` Andrew Lunn
2024-07-30 4:09 ` [PATCH net-next v5 13/14] microchip: lan865x: add driver support for Microchip's LAN865X MAC-PHY Parthiban Veerasooran
2024-07-30 4:15 ` Randy Dunlap
2024-07-31 7:55 ` Parthiban.Veerasooran [this message]
2024-07-30 6:16 ` Stefan Bigler
2024-07-31 8:03 ` Parthiban.Veerasooran
2024-08-11 16:09 ` Andrew Lunn
2024-08-12 9:39 ` Parthiban.Veerasooran
2024-07-30 4:09 ` [PATCH net-next v5 14/14] dt-bindings: net: add Microchip's LAN865X 10BASE-T1S MACPHY Parthiban Veerasooran
2024-07-30 15:17 ` Rob Herring
2024-07-31 4:29 ` Parthiban.Veerasooran
2024-08-11 15:59 ` Andrew Lunn
2024-07-30 20:29 ` [PATCH net-next v5 00/14] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface Andrew Lunn
2024-07-31 0:12 ` Jakub Kicinski
2024-07-31 4:39 ` Parthiban.Veerasooran
-- strict thread matches above, loose matches on Subject: below --
2024-07-26 12:38 Parthiban Veerasooran
2024-07-26 12:39 ` [PATCH net-next v5 13/14] microchip: lan865x: add driver support for Microchip's LAN865X MAC-PHY Parthiban Veerasooran
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=6acd6d65-7dfb-4b3d-9a39-edcc5728261f@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Pier.Beruto@onsemi.com \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=Steen.Hegelund@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=benjamin.bigler@bernformulastudent.ch \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@bigler.io \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=saeedm@nvidia.com \
--cc=vladimir.oltean@nxp.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 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).