From: Sean Nyekjaer <sean@geanix.com>
To: Dan Murphy <dmurphy@ti.com>, mkl@pengutronix.de
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] net: m_can: Make wake-up gpio an optional
Date: Thu, 5 Dec 2019 08:39:08 +0100 [thread overview]
Message-ID: <b9eaa5c4-13bc-295f-dcbf-d2a846243682@geanix.com> (raw)
In-Reply-To: <20191204175112.7308-2-dmurphy@ti.com>
On 04/12/2019 18.51, Dan Murphy wrote:
> The device has the ability to disable the wake-up pin option.
> The wake-up pin can be either force to GND or Vsup and does not have to
> be tied to a GPIO. In order for the device to not use the wake-up feature
> write the register to disable the WAKE_CONFIG option.
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> CC: Sean Nyekjaer <sean@geanix.com>
Reviewed-by: Sean Nyekjaer <sean@geanix.com>
> ---
Hi Dan,
I would add tcan4x5x to the subject of this patch ->
"net: m_can: tcan4x5x Make wake-up gpio an optional"
Will be testing this during this or the next week...
/Sean
next prev parent reply other threads:[~2019-12-05 7:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 17:51 [PATCH 1/2] dt-bindings: tcan4x5x: Make wake-gpio an optional gpio Dan Murphy
2019-12-04 17:51 ` [PATCH 2/2] net: m_can: Make wake-up gpio an optional Dan Murphy
2019-12-05 7:39 ` Sean Nyekjaer [this message]
2019-12-05 13:26 ` Dan Murphy
2019-12-05 14:39 ` Marc Kleine-Budde
2019-12-05 15:01 ` Dan Murphy
2019-12-05 15:35 ` Marc Kleine-Budde
2019-12-09 21:01 ` Dan Murphy
2019-12-09 21:06 ` Marc Kleine-Budde
2019-12-09 21:07 ` Dan Murphy
2019-12-09 21:10 ` Marc Kleine-Budde
2019-12-05 7:36 ` [PATCH 1/2] dt-bindings: tcan4x5x: Make wake-gpio an optional gpio Sean Nyekjaer
2019-12-06 13:49 ` Sean Nyekjaer
2019-12-06 13:49 ` Sean Nyekjaer
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=b9eaa5c4-13bc-295f-dcbf-d2a846243682@geanix.com \
--to=sean@geanix.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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