From: Arnd Bergmann <arnd@arndb.de>
To: "Marek Behún" <marek.behun@nic.cz>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>, Shawn Guo <shawnguo@kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 bus+gpio 1/5] bus: Add support for Moxtet bus
Date: Tue, 5 Mar 2019 12:24:04 +0100 [thread overview]
Message-ID: <CAK8P3a2gfj++xu9ZFFx_3KoYFEtOr3HfUk_u1zwQ_8ubQAPdag@mail.gmail.com> (raw)
In-Reply-To: <20190301035852.26780-2-marek.behun@nic.cz>
On Fri, Mar 1, 2019 at 5:02 AM Marek Behún <marek.behun@nic.cz> wrote:
>
> On the Turris Mox router different modules can be connected to the main
> CPU board: currently a module with a SFP cage, a module with MiniPCIe
> connector, a 4-port switch module, an 8-port switch module, and a 4-port
> USB3 module.
>
> For example:
> [CPU]-[PCIe]-[8-port switch]-[8-port switch]-[SFP]
>
> Each of this modules has an input and output shift register, and these
> are connected via SPI to the CPU board.
>
> Via SPI we are able to discover which modules are connected, in which
> order, and we can also read some information about the modules or
> configure them.
> From each module 8 bits can be read (of which low 4 bits identify the
> module) and 8 bits can be written.
>
> For example from the module with a SFP cage we can read the LOS,
> TX-FAULT and MOD-DEF0 signals, while we can write TX-DISABLE and
> RATE-SELECT signals.
>
> This driver creates a new bus type, called "moxtet". For each Mox module
> it finds via SPI, it creates a new device on the moxtet bus so that
> drivers can be written for them.
>
> The topology of how Mox modules are connected can then be read by
> listing /sys/bus/moxtet/devices.
>
> Signed-off-by: Marek Behún <marek.behun@nic.cz>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
This looks very nice! I looked through the driver now and found nothing
to comment on other than the debugging properties that Linus already
mentioned, so please add my
Acked-by: Arnd Bergmann <arnd@arndb.de>
and submit the next version to soc@kernel.org so we can pick it up
for linux-5.2.
Arnd
next prev parent reply other threads:[~2019-03-05 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 3:58 [PATCH v3 bus+gpio 0/5] Add Moxtet bus and GPIO over Moxtet bus Marek Behún
2019-03-01 3:58 ` [PATCH v3 bus+gpio 1/5] bus: Add support for " Marek Behún
2019-03-05 11:24 ` Arnd Bergmann [this message]
2019-03-01 3:58 ` [PATCH v3 bus+gpio 2/5] dt-bindings: bus: Document moxtet bus binding Marek Behún
2019-03-01 3:58 ` [PATCH v3 bus+gpio 3/5] bus: moxtet: Add sysfs documentation Marek Behún
2019-03-01 14:34 ` Linus Walleij
2019-03-01 15:15 ` Marek Behun
2019-03-04 12:07 ` Linus Walleij
2019-03-05 11:11 ` Arnd Bergmann
2019-03-01 3:58 ` [PATCH v3 bus+gpio 4/5] drivers: gpio: Add support for GPIOs over Moxtet bus Marek Behún
2019-03-01 3:58 ` [PATCH v3 bus+gpio 5/5] dt-bindings: gpio: Document GPIOs via " Marek Behún
2019-03-01 14:36 ` Linus Walleij
2019-03-01 15:16 ` Marek Behun
2019-03-03 23:17 ` Marek Behun
2019-03-04 9:53 ` Linus Walleij
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=CAK8P3a2gfj++xu9ZFFx_3KoYFEtOr3HfUk_u1zwQ_8ubQAPdag@mail.gmail.com \
--to=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=shawnguo@kernel.org \
--cc=tony@atomide.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).