From: Roger Quadros <rogerq@ti.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
wg@grandegger.com, tony@atomide.com
Cc: jay.schroeder@garmin.com, linux-can@vger.kernel.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] net: can: c_can: Fix default pinmux glitch at init
Date: Tue, 7 Jul 2015 17:37:39 +0300 [thread overview]
Message-ID: <559BE433.9020308@ti.com> (raw)
In-Reply-To: <559BE3BE.2020608@ti.com>
On 07/07/15 17:35, Roger Quadros wrote:
> On 07/07/15 17:33, Marc Kleine-Budde wrote:
>> On 07/07/2015 04:27 PM, Roger Quadros wrote:
>>> From: "J.D. Schroeder" <jay.schroeder@garmin.com>
>>>
>>> The previous change 3973c526ae9c (net: can: c_can: Disable pins when
>>> CAN interface
>>> is down) causes a slight glitch on the pinctrl settings when used. Since
>>> commit ab78029 (drivers/pinctrl: grab default handles from device core),
>>> the device core will automatically set the default pins. This causes
>>> the pins to be momentarily set to the default and then to the sleep
>>> state in register_c_can_dev(). By adding an optional "enable" state,
>>> boards can set the default pin state to be disabled and avoid the
>>> glitch when the switch from default to sleep first occurs. If the
>>> "enable" state is not available c_can_pinctrl_select_state() falls
>>> back to using the "default" pinctrl state.
>>>
>>> [Roger Q] - Forward port to v4.2
>>>
>>> Signed-off-by: J.D. Schroeder <jay.schroeder@garmin.com>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>>> ---
>>> drivers/net/can/c_can/c_can.c | 13 ++++++++++++-
>>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/net/can/c_can/c_can.c
>>> b/drivers/net/can/c_can/c_can.c
>>> index 041525d..66e98e7 100644
>>> --- a/drivers/net/can/c_can/c_can.c
>>> +++ b/drivers/net/can/c_can/c_can.c
>>> @@ -605,7 +605,18 @@ static int c_can_start(struct net_device *dev)
>>> priv->can.state = CAN_STATE_ERROR_ACTIVE;
>>>
>>> /* activate pins */
>>> - pinctrl_pm_select_default_state(dev->dev.parent);
>>> +#ifdef CONFIG_PINCTRL
>>
>> Please remove the ifdef, AFAICS there are static inline noop functions
>> if CONFIG_PINCTRL switched off.
>
> yes, you are right.
On second thoughts
device->pins are not defined if CONFIG_PINCTRL is not set.
so we can't remove the #ifdef.
cheers,
-roger
>
>>
>>> + if (priv->device->pins) {
>>> + struct pinctrl_state *s;
>>> +
>>> + /* Attempt to use "active" if available else use "default" */
>>> + s = pinctrl_lookup_state(priv->device->pins->p, "active");
>>> + if (!IS_ERR(s))
>>> + pinctrl_select_state(priv->device->pins->p, s);
>>> + else
>>> + pinctrl_pm_select_default_state(dev->dev.parent);
>>> + }
>>> +#endif
>>> return 0;
>>> }
>>>
>>>
>>
>> Marc
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>, <wg@grandegger.com>,
<tony@atomide.com>
Cc: <jay.schroeder@garmin.com>, <linux-can@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] net: can: c_can: Fix default pinmux glitch at init
Date: Tue, 7 Jul 2015 17:37:39 +0300 [thread overview]
Message-ID: <559BE433.9020308@ti.com> (raw)
In-Reply-To: <559BE3BE.2020608@ti.com>
On 07/07/15 17:35, Roger Quadros wrote:
> On 07/07/15 17:33, Marc Kleine-Budde wrote:
>> On 07/07/2015 04:27 PM, Roger Quadros wrote:
>>> From: "J.D. Schroeder" <jay.schroeder@garmin.com>
>>>
>>> The previous change 3973c526ae9c (net: can: c_can: Disable pins when
>>> CAN interface
>>> is down) causes a slight glitch on the pinctrl settings when used. Since
>>> commit ab78029 (drivers/pinctrl: grab default handles from device core),
>>> the device core will automatically set the default pins. This causes
>>> the pins to be momentarily set to the default and then to the sleep
>>> state in register_c_can_dev(). By adding an optional "enable" state,
>>> boards can set the default pin state to be disabled and avoid the
>>> glitch when the switch from default to sleep first occurs. If the
>>> "enable" state is not available c_can_pinctrl_select_state() falls
>>> back to using the "default" pinctrl state.
>>>
>>> [Roger Q] - Forward port to v4.2
>>>
>>> Signed-off-by: J.D. Schroeder <jay.schroeder@garmin.com>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>>> ---
>>> drivers/net/can/c_can/c_can.c | 13 ++++++++++++-
>>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/net/can/c_can/c_can.c
>>> b/drivers/net/can/c_can/c_can.c
>>> index 041525d..66e98e7 100644
>>> --- a/drivers/net/can/c_can/c_can.c
>>> +++ b/drivers/net/can/c_can/c_can.c
>>> @@ -605,7 +605,18 @@ static int c_can_start(struct net_device *dev)
>>> priv->can.state = CAN_STATE_ERROR_ACTIVE;
>>>
>>> /* activate pins */
>>> - pinctrl_pm_select_default_state(dev->dev.parent);
>>> +#ifdef CONFIG_PINCTRL
>>
>> Please remove the ifdef, AFAICS there are static inline noop functions
>> if CONFIG_PINCTRL switched off.
>
> yes, you are right.
On second thoughts
device->pins are not defined if CONFIG_PINCTRL is not set.
so we can't remove the #ifdef.
cheers,
-roger
>
>>
>>> + if (priv->device->pins) {
>>> + struct pinctrl_state *s;
>>> +
>>> + /* Attempt to use "active" if available else use "default" */
>>> + s = pinctrl_lookup_state(priv->device->pins->p, "active");
>>> + if (!IS_ERR(s))
>>> + pinctrl_select_state(priv->device->pins->p, s);
>>> + else
>>> + pinctrl_pm_select_default_state(dev->dev.parent);
>>> + }
>>> +#endif
>>> return 0;
>>> }
>>>
>>>
>>
>> Marc
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-07 14:37 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 [this message]
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
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=559BE433.9020308@ti.com \
--to=rogerq@ti.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=tony@atomide.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.