From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Rob Herring <robh@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org,
Marek Vasut <marek.vasut@gmail.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH] arm64: dts: renesas: r8a77990: ebisu: Add and enable CAN,FD device nodes
Date: Wed, 21 Nov 2018 11:20:46 +0100 [thread overview]
Message-ID: <20181121102046.vbimumaycuj225op@verge.net.au> (raw)
In-Reply-To: <20181119105508.GC932@kunai>
On Mon, Nov 19, 2018 at 11:55:08AM +0100, Wolfram Sang wrote:
>
> > > Same here, what was tested?
> >
> > I connected the CN10 to Peak CANFD, brought both interfaces up at
> > 125kBd/250kBd for FD
> > $ ip link set canX up type can bitrate 125000 dbitrate 250000 fd on
> >
> > And ran on either side:
> > $ cangen -m canX
> > and
> > $ candump -t d -dex canX
> > This should give a good mix of CAN messages.
>
> Perfect, thanks!
Thanks, applied for v4.21.
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Marek Vasut <marek.vasut@gmail.com>,
devicetree@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: r8a77990: ebisu: Add and enable CAN,FD device nodes
Date: Wed, 21 Nov 2018 11:20:46 +0100 [thread overview]
Message-ID: <20181121102046.vbimumaycuj225op@verge.net.au> (raw)
In-Reply-To: <20181119105508.GC932@kunai>
On Mon, Nov 19, 2018 at 11:55:08AM +0100, Wolfram Sang wrote:
>
> > > Same here, what was tested?
> >
> > I connected the CN10 to Peak CANFD, brought both interfaces up at
> > 125kBd/250kBd for FD
> > $ ip link set canX up type can bitrate 125000 dbitrate 250000 fd on
> >
> > And ran on either side:
> > $ cangen -m canX
> > and
> > $ candump -t d -dex canX
> > This should give a good mix of CAN messages.
>
> Perfect, thanks!
Thanks, applied for v4.21.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: renesas: r8a77990: ebisu: Add and enable CAN,FD device nodes
Date: Wed, 21 Nov 2018 11:20:46 +0100 [thread overview]
Message-ID: <20181121102046.vbimumaycuj225op@verge.net.au> (raw)
In-Reply-To: <20181119105508.GC932@kunai>
On Mon, Nov 19, 2018 at 11:55:08AM +0100, Wolfram Sang wrote:
>
> > > Same here, what was tested?
> >
> > I connected the CN10 to Peak CANFD, brought both interfaces up at
> > 125kBd/250kBd for FD
> > $ ip link set canX up type can bitrate 125000 dbitrate 250000 fd on
> >
> > And ran on either side:
> > $ cangen -m canX
> > and
> > $ candump -t d -dex canX
> > This should give a good mix of CAN messages.
>
> Perfect, thanks!
Thanks, applied for v4.21.
next prev parent reply other threads:[~2018-11-21 10:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 17:34 [PATCH] arm64: dts: renesas: r8a77990: ebisu: Add and enable CAN, FD device nodes Marek Vasut
2018-11-18 17:34 ` Marek Vasut
2018-11-18 17:34 ` [PATCH] arm64: dts: renesas: r8a77990: ebisu: Add and enable CAN,FD " Marek Vasut
2018-11-18 23:03 ` Wolfram Sang
2018-11-18 23:03 ` Wolfram Sang
2018-11-18 23:03 ` Wolfram Sang
2018-11-18 23:45 ` Marek Vasut
2018-11-18 23:45 ` Marek Vasut
2018-11-18 23:45 ` Marek Vasut
2018-11-19 10:55 ` Wolfram Sang
2018-11-19 10:55 ` Wolfram Sang
2018-11-19 10:55 ` Wolfram Sang
2018-11-21 10:20 ` Simon Horman [this message]
2018-11-21 10:20 ` Simon Horman
2018-11-21 10:20 ` 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=20181121102046.vbimumaycuj225op@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.