linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yang, Wenyou" <Wenyou.Yang@Microchip.com>
To: Faiz Abbas <faiz_abbas@ti.com>, <wg@grandegger.com>,
	<mkl@pengutronix.de>, <robh+dt@kernel.org>,
	<mark.rutland@arm.com>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<nsekhar@ti.com>, <fcooper@ti.com>, <robh@kernel.org>,
	<sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH v6 0/6] Add M_CAN Support for Dra76 platform
Date: Fri, 29 Dec 2017 11:38:10 +0800	[thread overview]
Message-ID: <667c651b-cb9b-4e71-437f-2cd3be39f491@Microchip.com> (raw)
In-Reply-To: <1513949488-13026-1-git-send-email-faiz_abbas@ti.com>



On 2017/12/22 21:31, Faiz Abbas wrote:
> This patch series adds support for M_CAN on the TI Dra76
> platform. Device tree patches will be sent separately.
> A bunch of patches were sent before by
> Franklin Cooper <fcooper@ti.com>. I have clubbed the
> series together and rebased to the latest kernel.
Tested this series on SAMA5D2 Xplained board.

Tested-by: Wenyou Yang <wenyou.yang@microchip.com>

>
> v6 changes:
> Dropped the patches to make hclk optional. Drivers
> which enable hclk as the interface clock using
> pm_runtime calls must still provide a hclk in the
> clocks property.
>
> Support higher speed CAN-FD bitrate:
> The community decided that data sampling point be used
> for the secondary sampling point here
> https://patchwork.kernel.org/patch/9909845/
>
> Franklin S Cooper Jr (6):
>    can: dev: Add support for limiting configured bitrate
>    can: m_can: Add call to of_can_transceiver
>    can: m_can: Add PM Runtime
>    can: m_can: Support higher speed CAN-FD bitrates
>    dt-bindings: can: m_can: Document new can transceiver binding
>    dt-bindings: can: can-transceiver: Document new binding
>
>   .../bindings/net/can/can-transceiver.txt           | 24 +++++++
>   .../devicetree/bindings/net/can/m_can.txt          |  9 +++
>   drivers/net/can/dev.c                              | 39 +++++++++++
>   drivers/net/can/m_can/m_can.c                      | 81 ++++++++++++++++++++--
>   include/linux/can/dev.h                            |  8 +++
>   5 files changed, 156 insertions(+), 5 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/net/can/can-transceiver.txt
>

Best Regards,
Wenyou Yang

      parent reply	other threads:[~2017-12-29  3:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 13:31 [PATCH v6 0/6] Add M_CAN Support for Dra76 platform Faiz Abbas
2017-12-22 13:31 ` [PATCH v6 1/6] can: dev: Add support for limiting configured bitrate Faiz Abbas
2018-01-02 13:00   ` Marc Kleine-Budde
2018-01-03 12:19     ` Faiz Abbas
2018-01-02 16:15   ` Marc Kleine-Budde
2018-01-03 12:21     ` Faiz Abbas
2017-12-22 13:31 ` [PATCH v6 2/6] can: m_can: Add call to of_can_transceiver Faiz Abbas
2017-12-22 13:31 ` [PATCH v6 3/6] can: m_can: Add PM Runtime Faiz Abbas
2018-01-02 16:07   ` Marc Kleine-Budde
2018-01-03 12:39     ` Faiz Abbas
2018-01-03 14:25       ` Marc Kleine-Budde
2018-01-03 15:06         ` Faiz Abbas
2018-01-03 15:17           ` Marc Kleine-Budde
2018-01-04 15:17             ` Faiz Abbas
2018-01-04 15:18               ` Marc Kleine-Budde
2018-01-05  1:23               ` Yang, Wenyou
2017-12-22 13:31 ` [PATCH v6 4/6] can: m_can: Support higher speed CAN-FD bitrates Faiz Abbas
2018-01-02 13:35   ` Marc Kleine-Budde
2018-01-03 12:55     ` Faiz Abbas
2017-12-22 13:31 ` [PATCH v6 5/6] dt-bindings: can: m_can: Document new can transceiver binding Faiz Abbas
2017-12-22 13:31 ` [PATCH v6 6/6] dt-bindings: can: can-transceiver: Document new binding Faiz Abbas
2017-12-29  3:38 ` Yang, Wenyou [this message]

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=667c651b-cb9b-4e71-437f-2cd3be39f491@Microchip.com \
    --to=wenyou.yang@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=faiz_abbas@ti.com \
    --cc=fcooper@ti.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --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).