From: Arnd Bergmann <arnd@arndb.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: devicetree@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Olof Johansson <olof@lixom.net>,
Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH] of/platform: export of_default_bus_match_table
Date: Tue, 05 Jan 2016 12:48:29 +0100 [thread overview]
Message-ID: <4336094.nx25lSVlfU@wuerfel> (raw)
In-Reply-To: <CAK7LNAR3yxRoQ-qLCASAaCwzCZaSiXMbRjasfWf=X1O9P49fgw@mail.gmail.com>
On Tuesday 05 January 2016 19:50:31 Masahiro Yamada wrote:
> 2016-01-05 19:13 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> > On Tuesday 05 January 2016 11:17:53 Masahiro Yamada wrote:
>
> This bus is used to connect external (on-board) devices with the SoC.
>
> So, no possibility for AMBA, but
> I want "simple-bus" for grouping some device nodes.
> Also, "simple-mfd" would be useful because an external device could be an MFD.
>
>
> Please see arch/arm/boot/dts/uniphier-support-card.dtsi
>
> It describes an add-on card (expansion board)
> which has ETHER, UART, etc. on it.
>
> I implemented it as "simple-bus".
>
> This card is connected to the chip select 1
> of the UniPhier System Bus.
>
Ok, got it. So you could alternatively define your own match table
in the driver with just "simple-bus" and "simple-mfd". I think either
way is fine, let's see what the DT maintainers prefer.
Arnd
next prev parent reply other threads:[~2016-01-05 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 2:17 [PATCH] of/platform: export of_default_bus_match_table Masahiro Yamada
2016-01-05 10:13 ` Arnd Bergmann
2016-01-05 10:50 ` Masahiro Yamada
2016-01-05 11:48 ` Arnd Bergmann [this message]
2016-01-05 14:21 ` Rob Herring
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=4336094.nx25lSVlfU@wuerfel \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@kernel.org \
--cc=yamada.masahiro@socionext.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