All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Roger Quadros <rogerq@ti.com>,
	wg@grandegger.com, jay.schroeder@garmin.com,
	linux-can@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: dra7x-evm: Prevent glitch on DCAN1 pinmux
Date: Sun, 12 Jul 2015 23:29:06 -0700	[thread overview]
Message-ID: <20150713062906.GA26485@atomide.com> (raw)
In-Reply-To: <55A2BD97.8080006@pengutronix.de>

* Marc Kleine-Budde <mkl@pengutronix.de> [150712 12:22]:
> On 07/09/2015 08:34 PM, Marc Kleine-Budde wrote:
> > On 07/07/2015 04:27 PM, Roger Quadros wrote:
> >> Driver core sets "default" pinmux on on probe and CAN driver
> >> sets "sleep" pinmux during register. This causes a small window
> >> where the CAN pins are in "default" state with the DCAN module
> >> being disabled.
> >>
> >> Change the "default" state to be like sleep so this glitch is
> >> avoided. Add a new "active" state that is used by the driver
> >> when CAN is actually active.
> > 
> > Who is taking care of this patch? I'm applying 1/2 (v2) to linux-can,
> > should I take this patch, too?
> 
> I've included this patch in my pull request.

That's fine thanks there should not be any merge conflicts.

For things going in during the merge windows we need to worry
about the dts merge conflicts. Usually not a problem for fixes.

Regards,

Tony

      reply	other threads:[~2015-07-13  6:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 14:27 [PATCH 0/2] ARM: dra7: fix DCAN glitch Roger Quadros
2015-07-07 14:27 ` Roger Quadros
2015-07-07 14:27 ` [PATCH 1/2] net: can: c_can: Fix default pinmux glitch at init Roger Quadros
2015-07-07 14:27   ` Roger Quadros
2015-07-07 14:33   ` Marc Kleine-Budde
2015-07-07 14:35     ` Roger Quadros
2015-07-07 14:35       ` Roger Quadros
2015-07-07 14:37       ` Roger Quadros
2015-07-07 14:37         ` Roger Quadros
2015-07-07 14:43         ` Marc Kleine-Budde
2015-07-08  8:09           ` Roger Quadros
2015-07-08  8:09             ` Roger Quadros
2015-07-08  8:17             ` Marc Kleine-Budde
2015-07-07 15:49         ` Grygorii Strashko
2015-07-07 15:49           ` Grygorii Strashko
2015-07-08  8:13           ` Roger Quadros
2015-07-08  8:13             ` Roger Quadros
2015-07-08 10:31             ` Grygorii Strashko
2015-07-08 10:31               ` Grygorii Strashko
2015-07-08 10:44               ` Roger Quadros
2015-07-08 10:44                 ` Roger Quadros
2015-07-08 11:38   ` [PATCH v2 " Roger Quadros
2015-07-08 11:38     ` Roger Quadros
2015-07-09 10:58     ` Grygorii Strashko
2015-07-09 10:58       ` Grygorii Strashko
2015-07-09 10:59       ` Marc Kleine-Budde
2015-07-09 11:19         ` Grygorii Strashko
2015-07-09 11:19           ` Grygorii Strashko
2015-07-07 14:27 ` [PATCH 2/2] ARM: dts: dra7x-evm: Prevent glitch on DCAN1 pinmux Roger Quadros
2015-07-07 14:27   ` Roger Quadros
2015-07-09 18:34   ` Marc Kleine-Budde
2015-07-12 19:18     ` Marc Kleine-Budde
2015-07-13  6:29       ` Tony Lindgren [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=20150713062906.GA26485@atomide.com \
    --to=tony@atomide.com \
    --cc=jay.schroeder@garmin.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=rogerq@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.