From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Murphy Subject: Re: [PATCH 2/2] net: m_can: Make wake-up gpio an optional Date: Mon, 9 Dec 2019 15:01:30 -0600 Message-ID: References: <20191204175112.7308-1-dmurphy@ti.com> <20191204175112.7308-2-dmurphy@ti.com> <827b022e-9188-7bcf-25e3-3777df3b08a5@ti.com> <809b9ff1-88e3-4e46-33e0-856db37898b2@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <809b9ff1-88e3-4e46-33e0-856db37898b2@pengutronix.de> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Marc Kleine-Budde , Sean Nyekjaer Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org List-Id: linux-can.vger.kernel.org Marc On 12/5/19 8:39 AM, Marc Kleine-Budde wrote: > On 12/5/19 2:26 PM, Dan Murphy wrote: >> On 12/5/19 1:39 AM, Sean Nyekjaer wrote: >>> >>> 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 >>>> CC: Sean Nyekjaer >>> Reviewed-by: Sean Nyekjaer >>>> --- >>> >>> Hi Dan, >>> >>> I would add tcan4x5x to the subject of this patch -> >>> "net: m_can: tcan4x5x Make wake-up gpio an optional" >>> >> Do you want me to submit v2 with the $subject change? >> >> Or would you fix it up when committing it? > I'll change the subject while applying. > > Dan, what about maintainerchip of the tcan4x5? Do you know when you will be applying these? I have 2 patches I need to put on top. Dan > regards, > Marc >