On Thu, Aug 15, 2013 at 11:28 PM, Hanumant Singh
wrote:
> On 8/15/2013 1:47 PM, Linus Walleij wrote:
>> What pin groups and functions that exist on a SoC is what you put into
>> a SoC driver. Because this is a hardware characteristic.
>>
>> How these are combined on a board into different states
On Thu, Aug 15, 2013 at 11:28 PM, Hanumant Singh
hanum...@codeaurora.org wrote:
On 8/15/2013 1:47 PM, Linus Walleij wrote:
What pin groups and functions that exist on a SoC is what you put into
a SoC driver. Because this is a hardware characteristic.
How these are combined on a board into
On 8/15/2013 4:10 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 02:58:31PM -0700, Hanumant Singh wrote:
On 8/15/2013 2:50 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39
On Thu, Aug 15, 2013 at 02:58:31PM -0700, Hanumant Singh wrote:
> On 8/15/2013 2:50 PM, Josh Cartwright wrote:
> >On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
> >>On 8/14/2013 12:29 PM, Linus Walleij wrote:
> >>>On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson wrote:
> On
On 8/15/2013 2:50 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh wrote:
As a general note on the
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
> On 8/14/2013 12:29 PM, Linus Walleij wrote:
> >On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson wrote:
> >>On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh
> >>wrote:
> >
> >>As a general note on the patch, the pins and pin groups
On 8/15/2013 1:47 PM, Linus Walleij wrote:
On Thu, Aug 15, 2013 at 7:44 PM, Hanumant Singh wrote:
Ok i can switch to using pin groups defined in per soc files.
But in our case we have one soc going into different types of boards.
(atleast 3). In each of the boards the same external devices
On Thu, Aug 15, 2013 at 7:44 PM, Hanumant Singh wrote:
> Ok i can switch to using pin groups defined in per soc files.
> But in our case we have one soc going into different types of boards.
> (atleast 3). In each of the boards the same external devices end up using
> different pins. For ex
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh wrote:
As a general note on the patch, the pins and pin groups are defined by
the soc, I'm therefore not convinced that these should be
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson bj...@kryo.se wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh hanum...@codeaurora.org wrote:
As a general note on the patch, the pins and pin groups are defined by
the soc, I'm therefore not
On Thu, Aug 15, 2013 at 7:44 PM, Hanumant Singh hanum...@codeaurora.org wrote:
Ok i can switch to using pin groups defined in per soc files.
But in our case we have one soc going into different types of boards.
(atleast 3). In each of the boards the same external devices end up using
On 8/15/2013 1:47 PM, Linus Walleij wrote:
On Thu, Aug 15, 2013 at 7:44 PM, Hanumant Singh hanum...@codeaurora.org wrote:
Ok i can switch to using pin groups defined in per soc files.
But in our case we have one soc going into different types of boards.
(atleast 3). In each of the boards the
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson bj...@kryo.se wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh hanum...@codeaurora.org
wrote:
As a general note on the patch,
On 8/15/2013 2:50 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson bj...@kryo.se wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh
On Thu, Aug 15, 2013 at 02:58:31PM -0700, Hanumant Singh wrote:
On 8/15/2013 2:50 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson bj...@kryo.se wrote:
On
On 8/15/2013 4:10 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 02:58:31PM -0700, Hanumant Singh wrote:
On 8/15/2013 2:50 PM, Josh Cartwright wrote:
On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
On 8/14/2013 12:29 PM, Linus Walleij wrote:
On Tue, Jul 30, 2013 at 1:39
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson wrote:
> On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh
> wrote:
> As a general note on the patch, the pins and pin groups are defined by
> the soc, I'm therefore not convinced that these should be configured
> from the devicetree. It's at
On Wed, Aug 7, 2013 at 6:00 PM, Stephen Warren wrote:
> On 08/06/2013 05:45 PM, Hanumant Singh wrote:
>> Any comments on this?
>
> No. As I said, I personally want to see all the pingroups defined in the
> pinctrl driver. But, if someone else acks/... the patches without it, I
> probably won't
On Wed, Aug 7, 2013 at 6:00 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 08/06/2013 05:45 PM, Hanumant Singh wrote:
Any comments on this?
No. As I said, I personally want to see all the pingroups defined in the
pinctrl driver. But, if someone else acks/... the patches without it, I
On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson bj...@kryo.se wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh hanum...@codeaurora.org
wrote:
As a general note on the patch, the pins and pin groups are defined by
the soc, I'm therefore not convinced that these should be configured
On 7/29/2013 4:39 PM, Bjorn Andersson wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
On 08/06/2013 05:45 PM, Hanumant Singh wrote:
> On 7/31/2013 5:17 PM, Hanumant Singh wrote:
>> On 7/31/2013 2:06 PM, Stephen Warren wrote:
>>> On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
> On 07/30/2013 06:13 PM, Hanumant Singh wrote:
>>
On 08/06/2013 05:45 PM, Hanumant Singh wrote:
On 7/31/2013 5:17 PM, Hanumant Singh wrote:
On 7/31/2013 2:06 PM, Stephen Warren wrote:
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM,
On 7/29/2013 4:39 PM, Bjorn Andersson wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh hanum...@codeaurora.org wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the
On 7/31/2013 5:17 PM, Hanumant Singh wrote:
On 7/31/2013 2:06 PM, Stephen Warren wrote:
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM,
On 7/31/2013 5:17 PM, Hanumant Singh wrote:
On 7/31/2013 2:06 PM, Stephen Warren wrote:
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM,
On 7/31/2013 2:06 PM, Stephen Warren wrote:
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM,
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
> On 7/30/2013 8:59 PM, Stephen Warren wrote:
>> On 07/30/2013 06:13 PM, Hanumant Singh wrote:
>>> On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
> On 7/30/2013 2:22 PM, Stephen Warren wrote:
>>
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10
On 7/31/2013 2:06 PM, Stephen Warren wrote:
On 07/31/2013 01:46 PM, Hanumant Singh wrote:
On 7/30/2013 8:59 PM, Stephen Warren wrote:
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM,
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
> On 7/30/2013 5:08 PM, Stephen Warren wrote:
>> On 07/30/2013 06:01 PM, Hanumant Singh wrote:
>>> On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
> We actually have the same TLMM pinmux used by
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a family.
The number of pins on each soc may vary.
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
> On 7/30/2013 2:22 PM, Stephen Warren wrote:
>> On 07/30/2013 03:10 PM, hanumant wrote:
>> ...
>>> We actually have the same TLMM pinmux used by several socs of a family.
>>> The number of pins on each soc may vary.
>>> Also a given soc gets used in a
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a family.
The number of pins on each soc may vary.
Also a given soc gets used in a number of boards.
The device tree for a given soc is split
On 07/30/2013 03:10 PM, hanumant wrote:
...
> We actually have the same TLMM pinmux used by several socs of a family.
> The number of pins on each soc may vary.
> Also a given soc gets used in a number of boards.
> The device tree for a given soc is split into the different boards that
> its in ie
On 7/29/2013 9:37 AM, Linus Walleij wrote:
On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This
On 7/29/2013 9:37 AM, Linus Walleij wrote:
On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
hanum...@codeaurora.org wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a family.
The number of pins on each soc may vary.
Also a given soc gets used in a number of boards.
The device tree for a given soc is split into the different boards that
its in ie the
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a family.
The number of pins on each soc may vary.
Also a given soc gets used in a number of boards.
The device tree for a given soc is split
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a family.
The number of pins on each soc may vary.
Also a given soc gets used in a number of
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a family.
The number of pins on each soc may vary.
On 07/30/2013 06:13 PM, Hanumant Singh wrote:
On 7/30/2013 5:08 PM, Stephen Warren wrote:
On 07/30/2013 06:01 PM, Hanumant Singh wrote:
On 7/30/2013 2:22 PM, Stephen Warren wrote:
On 07/30/2013 03:10 PM, hanumant wrote:
...
We actually have the same TLMM pinmux used by several socs of a
On 07/29/2013 10:37 AM, Linus Walleij wrote:
> On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
> wrote:
>
>> Add a new device tree enabled pinctrl driver for
>> Qualcomm MSM SoC's. This driver provides an extensible
>> framework to interface all MSM's that use a TLMM pinmux,
>> with the pinctrl
On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
wrote:
> Add a new device tree enabled pinctrl driver for
> Qualcomm MSM SoC's. This driver provides an extensible
> framework to interface all MSM's that use a TLMM pinmux,
> with the pinctrl subsytem.
>
> This driver is split into two parts: the
On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
hanum...@codeaurora.org wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This driver is split
On 07/29/2013 10:37 AM, Linus Walleij wrote:
On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
hanum...@codeaurora.org wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This driver is split into two parts: the pinctrl interface
and the TLMM version specific implementation. The
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This driver is split into two parts: the pinctrl interface
and the TLMM version specific implementation. The
On 06/27/2013 01:26 AM, Linus Walleij wrote:
> On Tue, Jun 25, 2013 at 7:41 PM, hanumant wrote:
>> On 06/24/2013 05:18 AM, Linus Walleij wrote:
>
+ The following pin configurations are properties are supported by SDC
pins
+ - qcom,sdc1-clk-pull: Pull up/down configuration SDC1
On Tue, Jun 25, 2013 at 7:41 PM, hanumant wrote:
> On 06/24/2013 05:18 AM, Linus Walleij wrote:
>>> + The following pin configurations are properties are supported by SDC pins
>>> + - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
>>> + - qcom,sdc1-clk-drv: Drive strength
On Tue, Jun 25, 2013 at 7:41 PM, hanumant hanum...@codeaurora.org wrote:
On 06/24/2013 05:18 AM, Linus Walleij wrote:
+ The following pin configurations are properties are supported by SDC pins
+ - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
+ - qcom,sdc1-clk-drv: Drive
On 06/27/2013 01:26 AM, Linus Walleij wrote:
On Tue, Jun 25, 2013 at 7:41 PM, hanumant hanum...@codeaurora.org wrote:
On 06/24/2013 05:18 AM, Linus Walleij wrote:
+ The following pin configurations are properties are supported by SDC
pins
+ - qcom,sdc1-clk-pull: Pull up/down
On 06/24/2013 05:18 AM, Linus Walleij wrote:
>> +
>> + - qcom,gp-pull: Pull up/down configuration.
>> + - qcom,gp-drv: Drive strength configuration.
>> + - qcom,gp-dir: Pull up/down configuration in power down mode.
>
> Rebase this to use the generic pin config mappings and parsing
> code
On 06/24/2013 05:18 AM, Linus Walleij wrote:
+
+ - qcom,gp-pull: Pull up/down configuration.
+ - qcom,gp-drv: Drive strength configuration.
+ - qcom,gp-dir: Pull up/down configuration in power down mode.
Rebase this to use the generic pin config mappings and parsing
code that can be
On Fri, Jun 21, 2013 at 11:52 PM, Hanumant Singh
wrote:
> Add a new device tree enabled pinctrl driver for
> Qualcomm MSM SoC's. This driver provides an extensible
> framework to interface all MSM's that use a TLMM pinmux,
> with the pinctrl subsytem.
This is really nice.
> + The pin group
On Fri, Jun 21, 2013 at 11:52 PM, Hanumant Singh
hanum...@codeaurora.org wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This is really nice.
+
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This driver is split into two parts: the pinctrl interface
and the TLMM version specific implementation. The
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This driver is split into two parts: the pinctrl interface
and the TLMM version specific implementation. The
60 matches
Mail list logo
