From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Magnus Damm <magnus.damm@gmail.com>,
linux-can@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH can-next 1/2] CAN: rcar: add gen[12] fallback compatibility strings
Date: Mon, 22 Feb 2016 16:40:39 +0100 [thread overview]
Message-ID: <CAMuHMdX3VjAZzhNxuucBn3hSS3YMmhJPVxpA2VKM+X-Qs3gxLg@mail.gmail.com> (raw)
In-Reply-To: <1456107350-12100-2-git-send-email-horms+renesas@verge.net.au>
On Mon, Feb 22, 2016 at 3:15 AM, Simon Horman
<horms+renesas@verge.net.au> wrote:
> Add fallback compatibility string for R-Car Gen 1 and Gen2 families.
> This is in keeping with the fallback scheme being adopted wherever
> appropriate for drivers for Renesas SoCs.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> Documentation/devicetree/bindings/net/can/rcar_can.txt | 4 +++-
> drivers/net/can/rcar_can.c | 2 ++
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/net/can/rcar_can.txt b/Documentation/devicetree/bindings/net/can/rcar_can.txt
> index 002d8440bf66..036786e1f70d 100644
> --- a/Documentation/devicetree/bindings/net/can/rcar_can.txt
> +++ b/Documentation/devicetree/bindings/net/can/rcar_can.txt
> @@ -6,6 +6,8 @@ Required properties:
> "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
> "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
> "renesas,can-r8a7791" if CAN controller is a part of R8A7791 SoC.
> + "renesas,can-gen1" for a generic R-Car Gen1 compatible device.
> + "renesas,can-gen2" for a generic R-Car Gen2 compatible device.
"renesas,rcar-gen1-can", "renesas,rcar-gen2-can"?
(Yeah, "can" looks a lot like "rcar" ;-)
Nothing further to say about SoC-specific vs. generic compatible values?
> - reg: physical base address and size of the R-Car CAN register map.
> - interrupts: interrupt specifier for the sole interrupt.
> - clocks: phandles and clock specifiers for 3 CAN clock inputs.
> @@ -25,7 +27,7 @@ Example
> SoC common .dtsi file:
>
> can0: can@e6e80000 {
> - compatible = "renesas,can-r8a7791";
> + compatible = "renesas,can-r8a7791", "renesas,can-gen2";
"renesas,rcar-gen2-can".
> reg = <0 0xe6e80000 0 0x1000>;
> interrupts = <0 186 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&mstp9_clks R8A7791_CLK_RCAN0>,
> diff --git a/drivers/net/can/rcar_can.c b/drivers/net/can/rcar_can.c
> index bc46be39549d..c70a1f795933 100644
> --- a/drivers/net/can/rcar_can.c
> +++ b/drivers/net/can/rcar_can.c
> @@ -904,6 +904,8 @@ static const struct of_device_id rcar_can_of_table[] __maybe_unused = {
> { .compatible = "renesas,can-r8a7779" },
> { .compatible = "renesas,can-r8a7790" },
> { .compatible = "renesas,can-r8a7791" },
> + { .compatible = "renesas,can-gen1" },
> + { .compatible = "renesas,can-gen2" },
"renesas,rcar-gen1-can"
"renesas,rcar-gen2-can".
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-02-22 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 2:15 [PATCH can-next 0/2] CAN: rcar: add fallback and r8a779[234] bindings Simon Horman
2016-02-22 2:15 ` [PATCH can-next 1/2] CAN: rcar: add gen[12] fallback compatibility strings Simon Horman
2016-02-22 3:37 ` Rob Herring
2016-02-22 9:40 ` Marc Kleine-Budde
2016-02-23 0:08 ` Simon Horman
2016-02-22 15:40 ` Geert Uytterhoeven [this message]
2016-02-23 0:03 ` Simon Horman
2016-02-22 2:15 ` [PATCH can-next 2/2] CAN: rcar: add device tree support for r8a779[234] Simon Horman
2016-02-22 3:36 ` Rob Herring
2016-02-22 13:48 ` Geert Uytterhoeven
2016-02-23 0:02 ` Simon Horman
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=CAMuHMdX3VjAZzhNxuucBn3hSS3YMmhJPVxpA2VKM+X-Qs3gxLg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.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).