Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Gerhard Engleder <gerhard@engleder-embedded.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
netdev <netdev@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 2/5] dt-bindings: net: Add tsnep Ethernet controller
Date: Tue, 27 Jul 2021 22:33:27 +0200 [thread overview]
Message-ID: <CANr-f5ykgOHc1G2JQrTnMCFyQ35LbnWPH2pTKV07v-ucy_Zi1Q@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKq6H471iFoLWRGvNSLpaJmuF+feDFut2p+J725n3U4HA@mail.gmail.com>
On Tue, Jul 27, 2021 at 10:25 PM Rob Herring <robh+dt@kernel.org> wrote:
> > > tsnep is pretty generic. Only 1 version ever? Or differences are/will
> > > be discoverable by other means.
> >
> > Differences shall be detected by flags in the registers; e.g., a flag for
> > gate control support. Anyway a version may make sense. Can you
> > point to a good reference binding with versions? I did not find a
> > network controller binding with versions.
>
> Some of the SiFive IP blocks have versions. Version numbers are the
> exception though. Ideally they would correspond to some version of
> your FPGA image. I just don't want to see 'v1' because that sounds
> made up. The above string can mean 'v1' or whatever version you want.
> I'm fine if you just add some description here about feature flag
> registers.
I will do that.
Gerhard
next prev parent reply other threads:[~2021-07-27 20:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 19:45 [PATCH net-next 0/5] TSN endpoint Ethernet MAC driver Gerhard Engleder
2021-07-26 19:45 ` [PATCH net-next 1/5] dt-bindings: Add vendor prefix for Engleder Gerhard Engleder
2021-07-26 19:46 ` [PATCH net-next 2/5] dt-bindings: net: Add tsnep Ethernet controller Gerhard Engleder
2021-07-26 23:35 ` Rob Herring
2021-07-27 18:34 ` Gerhard Engleder
2021-07-27 20:25 ` Rob Herring
2021-07-27 20:33 ` Gerhard Engleder [this message]
2021-07-28 5:13 ` Michal Simek
2021-07-28 7:44 ` Gerhard Engleder
2021-07-28 10:55 ` Michal Simek
2021-07-28 20:14 ` Gerhard Engleder
2021-07-29 5:07 ` Michal Simek
2021-07-29 7:07 ` Gerhard Engleder
2021-07-29 7:57 ` Michal Simek
2021-07-26 19:46 ` [PATCH net-next 3/5] dt-bindings: arm: Add Engleder bindings Gerhard Engleder
2021-07-26 19:46 ` [PATCH net-next 4/5] tsnep: Add TSN endpoint Ethernet MAC driver Gerhard Engleder
2021-07-26 20:49 ` Andrew Lunn
2021-07-27 20:18 ` Gerhard Engleder
2021-07-26 21:15 ` Andrew Lunn
2021-07-27 20:49 ` Gerhard Engleder
2021-07-26 21:29 ` Andrew Lunn
2021-07-27 22:05 ` Gerhard Engleder
2021-07-27 22:41 ` Andrew Lunn
2021-07-28 8:24 ` Gerhard Engleder
2021-07-26 23:25 ` kernel test robot
2021-07-26 19:46 ` [PATCH net-next 5/5] arm64: dts: zynqmp: Add ZCU104 based TSN endpoint Gerhard Engleder
2021-07-26 23:40 ` Rob Herring
2021-07-27 20:10 ` Gerhard Engleder
2021-07-27 20:17 ` Rob Herring
2021-07-27 20:23 ` Gerhard Engleder
2021-07-28 5:10 ` Michal Simek
2021-07-28 8:19 ` Gerhard Engleder
2021-07-28 10:58 ` Michal Simek
2021-07-28 20:51 ` Gerhard Engleder
2021-07-29 5:22 ` Michal Simek
2021-07-29 6:47 ` Gerhard Engleder
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=CANr-f5ykgOHc1G2JQrTnMCFyQ35LbnWPH2pTKV07v-ucy_Zi1Q@mail.gmail.com \
--to=gerhard@engleder-embedded.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--subject='Re: [PATCH net-next 2/5] dt-bindings: net: Add tsnep Ethernet controller' \
/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
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).