From: Rob Herring <robh@kernel.org>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"mkl@pengutronix.de" <mkl@pengutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"wg@grandegger.com" <wg@grandegger.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
Aisheng DONG <aisheng.dong@nxp.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>
Subject: Re: [PATCH V6 1/2] Documentation: can: flexcan: add stop mode property to device tree
Date: Mon, 26 Nov 2018 14:06:19 -0600 [thread overview]
Message-ID: <20181126200619.GA1595@bogus> (raw)
In-Reply-To: <20181123083304.3232-2-qiangqing.zhang@nxp.com>
On Fri, 23 Nov 2018 08:35:29 +0000, Joakim Zhang wrote:
> From: Aisheng Dong <aisheng.dong@nxp.com>
>
> The FlexCAN controller can parse the stop mode property to enable CAN
> self wakeup feature.
>
> Signed-off-by: Aisheng Dong <aisheng.dong@nxp.com>
> Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
> ---
> ChangeLog:
> V1->V2:
> *add a vendor prefix in property (stop-mode -> fsl,stop-mode).
> V2->V6:
> *no change.
> ---
> Documentation/devicetree/bindings/net/can/fsl-flexcan.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-11-26 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 8:35 [PATCH V6 0/2] can: flexcan: add can self wakeup support Joakim Zhang
2018-11-23 8:35 ` [PATCH V6 1/2] Documentation: can: flexcan: add stop mode property to device tree Joakim Zhang
2018-11-26 20:06 ` Rob Herring [this message]
2018-11-23 8:35 ` [PATCH V6 2/2] can: flexcan: add self wakeup support Joakim Zhang
2018-11-23 15:03 ` Marc Kleine-Budde
2018-11-26 1:12 ` Joakim Zhang
2018-11-26 11:34 ` Marc Kleine-Budde
2018-11-23 8:56 ` [PATCH V6 0/2] can: flexcan: add can " Aisheng DONG
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=20181126200619.GA1595@bogus \
--to=robh@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@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).