From: Andrew Lunn <andrew@lunn.ch>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: Stuart Yoder <stuyoder@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
gregkh <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ruxandra Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com>,
Razvan Stefanescu <razvan.stefanescu@nxp.com>,
Roy Pledge <roy.pledge@nxp.com>,
Networking <netdev@vger.kernel.org>
Subject: Re: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support
Date: Thu, 5 Apr 2018 14:48:10 +0200 [thread overview]
Message-ID: <20180405124810.GE12178@lunn.ch> (raw)
In-Reply-To: <5AC61393.7090509@nxp.com>
> > Hi Laurentiu
> >
> > So i can use switchdev without it? I can modprobe the switchdev
> > driver, all the physical interfaces will appear, and i can use ip addr
> > add etc. I do not need to use a user space tool at all in order to use
> > the network functionality?
>
> Absolutely!
Great.
Then the easiest way forwards is to simply drop the IOCTL code for the
moment. Get the basic support for the hardware into the kernel
first. Then come back later to look at dynamic behaviour which needs
some form of configuration.
> In normal use cases the system designer, depending on the requirements,
> configures the various devices that it desires through a firmware
> configuration (think something like a device tree). The devices
> configured are presented on the mc-bus and probed normally by the
> kernel. The standard networking linux tools can be used as expected.
So what you should probably do is start a discussion on what this
device tree binding looks like. But you need to be careful even
here. Device tree describes the hardware, not how you configure the
hardware. So maybe DT does not actually fit.
Andrew
next prev parent reply other threads:[~2018-04-05 12:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1521818402.git.ioana.ciornei@nxp.com>
[not found] ` <d8c243a9ead2fe1375dee242aec26d1276129409.1521818402.git.ioana.ciornei@nxp.com>
[not found] ` <CAK8P3a089ZiPdp1CcVct8Kac+ejkNP8TrVpWYSr_nMGo4goO1Q@mail.gmail.com>
[not found] ` <HE1PR04MB32126A07A4B4CC7225E661E4E0A30@HE1PR04MB3212.eurprd04.prod.outlook.com>
2018-03-28 15:43 ` [PATCH v3 2/4] bus: fsl-mc: add restool userspace support Arnd Bergmann
2018-03-28 16:28 ` Andrew Lunn
2018-04-02 13:24 ` Ioana Ciornei
2018-04-02 13:44 ` Andrew Lunn
2018-04-03 11:12 ` Razvan Stefanescu
2018-04-03 13:04 ` Andrew Lunn
2018-04-03 23:57 ` Stuart Yoder
2018-04-04 1:05 ` Andrew Lunn
2018-04-04 3:22 ` Stuart Yoder
2018-04-04 12:42 ` Andrew Lunn
2018-04-05 4:24 ` Stuart Yoder
2018-04-05 10:30 ` Laurentiu Tudor
2018-04-05 11:47 ` Andrew Lunn
2018-04-05 12:16 ` Laurentiu Tudor
2018-04-05 12:48 ` Andrew Lunn [this message]
2018-04-05 14:43 ` Laurentiu Tudor
2018-04-05 15:23 ` Andrew Lunn
2018-04-05 15:35 ` Ruxandra Ioana Ciocoi Radulescu
2018-04-05 16:12 ` gregkh
2018-04-05 16:56 ` Andrew Lunn
2018-04-05 12:30 ` gregkh
2018-04-05 14:09 ` Laurentiu Tudor
2018-04-05 14:19 ` gregkh
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=20180405124810.GE12178@lunn.ch \
--to=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razvan.stefanescu@nxp.com \
--cc=roy.pledge@nxp.com \
--cc=ruxandra.radulescu@nxp.com \
--cc=stuyoder@gmail.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).