[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51A4B995.9050203@ti.com>
Date: Tue, 28 May 2013 19:35:09 +0530
From: Mugunthan V N <mugunthanvnm@...com>
To: Tony Lindgren <tony@...mide.com>
CC: <netdev@...r.kernel.org>, <devicetree-discuss@...ts.ozlabs.org>,
Hebbar Gururaja <gururaja.hebbar@...com>,
<benoit.cousson@...aro.org>, <linux-omap@...r.kernel.org>,
<davem@...emloft.net>
Subject: Re: [net-next PATCH v3 1/6] net: cpsw: enhance pinctrl support
On 5/28/2013 3:06 AM, Tony Lindgren wrote:
> * Mugunthan V N <mugunthanvnm@...com> [130526 11:28]:
>> From: Hebbar Gururaja <gururaja.hebbar@...com>
>>
>> Amend cpsw controller to optionally take a pin control handle and set
>> the state of the pins to:
>>
>> - "default" on boot, resume
>> - "sleep" on suspend()
>>
>> This should make it possible to optimize energy usage for the pins
>> for the suspend/resume cycle.
>>
>> If any of the above pin states are missing in dt, a warning message
>> about the missing state is displayed.
>> If certain pin-states are not available, to remove this warning message
>> pass respective state name with null phandler.
>>
>> Signed-off-by: Hebbar Gururaja <gururaja.hebbar@...com>
>> Signed-off-by: Mugunthan V N <mugunthanvnm@...com>
>> ---
>> drivers/net/ethernet/ti/cpsw.c | 48 ++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 48 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c
>> index 21a5b29..c9ed730 100644
>> --- a/drivers/net/ethernet/ti/cpsw.c
>> +++ b/drivers/net/ethernet/ti/cpsw.c
>> @@ -35,6 +35,7 @@
>> #include <linux/if_vlan.h>
>>
>> #include <linux/platform_data/cpsw.h>
>> +#include <linux/pinctrl/consumer.h>
>>
>> #include "cpsw_ale.h"
>> #include "cpts.h"
>> @@ -351,6 +352,11 @@ struct cpsw_priv {
>> bool irq_enabled;
>> struct cpts *cpts;
>> u32 emac_port;
>> +
>> + /* Two optional pin states - default & sleep */
>> + struct pinctrl *pinctrl;
>> + struct pinctrl_state *pins_def;
>> + struct pinctrl_state *pins_sleep;
>> };
> Which pins do you need to dynamically remux? If it's not all
> the pins, you should have three sets: default, active and idle.
> This way the static pins in the default group don't need to be
> constantly toggled.
>
> Regards,
>
> Tony
Tony
I am using this for all the pins, in probe all the cpsw pins will be
configured
and i have used the same in suspend/resume callback for power saving.
Regards
Mugunthan V N
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists