Linux CAN drivers development
 help / color / mirror / Atom feed
From: Sean Nyekjaer <sean@geanix.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	dmurphy@ti.com, linux-can@vger.kernel.org
Cc: martin@geanix.com, stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] can: m_can: tcan4x5x: put the device out of standby before register access
Date: Wed, 11 Dec 2019 12:28:21 +0100	[thread overview]
Message-ID: <ae996f9a-e50d-8f31-7457-c7fb461f5c9e@geanix.com> (raw)
In-Reply-To: <41d13619-fab8-ca19-c340-c80cd80d117e@pengutronix.de>



On 11/12/2019 10.44, Marc Kleine-Budde wrote:
> On 12/11/19 10:13 AM, Sean Nyekjaer wrote:
>>>> When the tcan device comes out of reset it comes out in standby mode.
>>>> The m_can driver tries to access the control register but fails due to
>>>> the device is in standby mode.
>>>> So this patch will put the tcan device in normal mode before the m_can
>>>> driver does the initialization.
>>>>
>>>> Fixes: a229abeed7f7 ("can: tcan4x5x: Turn on the power before parsing the config")
>>>> Cc: stable@vger.kernel.org
>>>> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
>>>
>>> Applied both to linux-can.
>>
>> Oh, the commit id for "can: tcan4x5x: Turn on the power before parsing
>> the config" have changed, since this morning :)
> 
> Ahh, I see.
> 
> Until there is a pull request (including a tag) the testing branch is
> subject to rebase. Meaning, when there is a patch, that needs update I'm
> happy to squash things into it.
> 
> I'm squashing there two commits into one:

It's two different authors :-)
> 
>> # This is a combination of 2 commits.
>> # This is the 1st commit message:
>>
>> can: tcan4x5x: Turn on the power before parsing the config
>>
>> The parse config function now performs action on the device either
>> reading or writing and a reset.  If the regulator is managed it needs
>> to be turned on.  So turn on the regulator if available if the parsing
>> fails then turn off the regulator.
>>
>> Fixes: a5235f3c7c23 ("can: tcan45x: Make wake-up GPIO an optional GPIO")
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
>>
>> # This is the commit message #2:
>>
>> can: tcan4x5x: put the device out of standby before register access
>>
>> The m_can tries to detect if Non ISO Operation is available while in
>> standby, this function results in the following error:
>>
>> tcan4x5x spi2.0 (unnamed net_device) (uninitialized): Failed to init module
>> tcan4x5x spi2.0: m_can device registered (irq=84, version=32)
>> tcan4x5x spi2.0 can2: TCAN4X5X successfully initialized.
>>
>> When the tcan device comes out of reset it comes out in standby mode.
>> The m_can driver tries to access the control register but fails due to
>> the device is in standby mode.
>>
>> So this patch will put the tcan device in normal mode before the m_can
>> driver does the initialization.
>>
>> Fixes: a229abeed7f7 ("can: tcan4x5x: Turn on the power before parsing the config")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
>> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> 
> Can you give me an updated commit message?
> 

I think it would be better to update the fixes tag :)

Could update the fixes tag for with the new commit id...

/Sean

  reply	other threads:[~2019-12-11 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  6:42 [PATCH v3 1/2] can: m_can: tcan4x5x: put the device out of standby before register access Sean Nyekjaer
2019-12-11  8:42 ` Marc Kleine-Budde
2019-12-11  9:13   ` Sean Nyekjaer
2019-12-11  9:44     ` Marc Kleine-Budde
2019-12-11 11:28       ` Sean Nyekjaer [this message]
2019-12-11 12:10         ` Marc Kleine-Budde
2019-12-11 12:15           ` Sean Nyekjaer
2019-12-11 12:35             ` Marc Kleine-Budde

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=ae996f9a-e50d-8f31-7457-c7fb461f5c9e@geanix.com \
    --to=sean@geanix.com \
    --cc=dmurphy@ti.com \
    --cc=linux-can@vger.kernel.org \
    --cc=martin@geanix.com \
    --cc=mkl@pengutronix.de \
    --cc=stable@vger.kernel.org \
    /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