On 24/09/13 23:04, Belisko Marek wrote:
> Hi,
>
> we're using connector-analog-tv driver to enable TV out on gta04
> board. There is exception that we need to change some twl registers +
> some gpio when enable/disable TV output. My question is if there is
> some way how to do that or do we need t
On Mon, Sep 23, 2013 at 11:41:03PM +0200, Thierry Reding wrote:
> The GPIO API defines 0 as being a valid GPIO number, so this field needs
> to be initialized explicitly.
>
> Signed-off-by: Thierry Reding
> ---
> arch/arm/mach-shmobile/board-armadillo800eva.c | 1 +
> 1 file changed, 1 insertion
On Tue, Sep 24, 2013 at 11:00:24AM +0200, Thierry Reding wrote:
> On Tue, Sep 24, 2013 at 05:14:46PM +0900, Simon Horman wrote:
> > [ Cc: Olof Johansson, Kevin Hilman and Arnd Bergman: arm-soc maintainers ]
> >
> > On Mon, Sep 23, 2013 at 11:40:57PM +0200, Thierry Reding wrote:
> > > This series a
On Tue, 24 Sep 2013, Rob Landley wrote:
> On 09/24/2013 04:48:00 PM, Russell King - ARM Linux wrote:
> > Now, if you feel strongly about this, we _could_ introduce a
> > CONFIG_OLD_BINUTILS and give everyone their cake - but it will be
> > fragile. Not everyone will remember to get that right, be
Here are some basic OMAP test results for Linux v3.12-rc2.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.12-rc2/20130924152551/
Test summary
Build: zImage:
Pass ( 2/ 2): omap2plus_defconfig, omap2plus_defconfig_am33xx_only
Build: uImage+dtb:
Pa
On 09/24/2013 04:48:00 PM, Russell King - ARM Linux wrote:
On Tue, Sep 24, 2013 at 04:23:48PM -0500, Rob Landley wrote:
> What value is there in requiring the new toolchain? From what I
could
> see of the commits it was micro-optimizations around memory
barriers.
>
> *shrug* I can revert the
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW should be fully configured/enabled as an IRQ if a driver solely
uses IRQ APIs such as
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW should be fully configured/enabled as an IRQ if a driver solely
uses IRQ APIs such as
The GPIO OMAP controller pins can be used as IRQ and GPIO
independently so is necessary to keep track GPIO pins and
IRQ lines usage separately to make sure that the bank will
always be enabled while being used.
Also move gpio_is_input() definition in preparation for the
next patch that setups the
> From: Suman Anna [mailto:s-a...@ti.com]
> Sent: Tuesday, September 24, 2013 4:48 PM
>
> On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
> > On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
> >>> From: Paul Zimmerman
> >>> Sent: Tuesday, September 24, 2013 1:21 PM
> >>>
> >>> Hi,
> >
On Tuesday 24 September 2013 07:48 PM, Suman Anna wrote:
> On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
>> On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
From: Paul Zimmerman
Sent: Tuesday, September 24, 2013 1:21 PM
Hi,
I have an OMAP5432 uEVM which
On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
> On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
>>> From: Paul Zimmerman
>>> Sent: Tuesday, September 24, 2013 1:21 PM
>>>
>>> Hi,
>>>
>>> I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
>>> (tried 3.11 and 3.12
On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
>> From: Paul Zimmerman
>> Sent: Tuesday, September 24, 2013 1:21 PM
>>
>> Hi,
>>
>> I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
>> (tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board (v6.0.0.7),
>> w
On Tue, Sep 24, 2013 at 04:23:48PM -0500, Rob Landley wrote:
> What value is there in requiring the new toolchain? From what I could
> see of the commits it was micro-optimizations around memory barriers.
>
> *shrug* I can revert the patch locally, or patch the extra instruction
> into my toolc
On 09/24/2013 07:11:38 AM, Måns Rullgård wrote:
Rob Landley writes:
> On 09/23/2013 06:59:17 PM, Pavel Machek wrote:
>> During 3.12-rc, Will Deacon introduced code into arch/arm that
>> requires binutils 2.22.
>
> Um, my toolchain is using the last gplv2 snapshot of binutils out of
> git, which
Hi,
On Tue, Sep 24, 2013 at 07:05:47PM +0200, Pali Rohár wrote:
> No, isp1704 driver is doing fastcharger detection (and then
> export charger type via sysfs power supply) based on musb usb
> events.
>
> Real charging (enabling/disabling and setting properties) is done
> by bq24150a chip which
> From: Paul Zimmerman
> Sent: Tuesday, September 24, 2013 1:21 PM
>
> Hi,
>
> I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
> (tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board (v6.0.0.7),
> which comes with 3.8.4 which works fine.
>
> I found this thread: h
Hi,
I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
(tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board (v6.0.0.7),
which comes with 3.8.4 which works fine.
I found this thread: http://marc.info/?l=fedora-arm&m=137717811815777 and
tried using git://git.kernel.org
* Stephen Warren [130924 13:03]:
> On 09/23/2013 05:46 PM, Sebastian Reichel wrote:
> > Hi,
> >
> > On Mon, Sep 23, 2013 at 02:35:35PM -0600, Stephen Warren wrote:
> >> On 09/15/2013 02:44 PM, Sebastian Reichel wrote:
> >>> Add SSI device tree data for OMAP34xx and Nokia N900.
>
> ...
> >>> +- t
Hi,
we're using connector-analog-tv driver to enable TV out on gta04
board. There is exception that we need to change some twl registers +
some gpio when enable/disable TV output. My question is if there is
some way how to do that or do we need to copy'n'paste code from
connector-analog-tv driver
On 09/23/2013 05:46 PM, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Sep 23, 2013 at 02:35:35PM -0600, Stephen Warren wrote:
>> On 09/15/2013 02:44 PM, Sebastian Reichel wrote:
>>> Add SSI device tree data for OMAP34xx and Nokia N900.
...
>>> +- ti,hwmods: Name of the hwmod associated
Add minimal DT support for Nokia N950 & N9 phones. The same functionality
that is provided by the current board file should work: serial console,
USB, OneNAND and MMC.
Signed-off-by: Aaro Koskinen
---
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/omap3-n9.dts | 18
Delete board file for Nokia RM-680/RM-696 (N950/N9). DT-based booting
should be used for further development on this HW.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap2/Kconfig | 7 --
arch/arm/mach-omap2/Makefile | 1 -
arch/arm/mach-omap2/board-rm680.c | 167 ---
Set internal clock source for MMC2 on N950/N9.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap2/pdata-quirks.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/mach-omap2/pdata-quirks.c
b/arch/arm/mach-omap2/pdata-quirks.c
index 52b4bc3..1a7f492 100644
--- a/ar
Hi,
This adds DTS for N950/N9 and removes the legacy board file.
The following patches needs to be applied first:
http://marc.info/?l=linux-omap&m=137969869426861&w=2 (the whole series)
[PATCH 0/4] Clean up legacy platform data handling for omaps for v3.13
http://marc.info/?l=linux-oma
On Tue, 2013-09-24 at 19:41 +0200, Uwe Kleine-König wrote:
> CLKDEV_LOOKUP selects HAVE_CLK and COMMON_CLK selects CLKDEV_LOOKUP. So
> all symbols that select at least two of these symbols can be simplified.
>
> For imx, omap2 and ux500 some rearrangements were necessary before the
> simplificatio
On 09/24, Uwe Kleine-K??nig wrote:
> CLKDEV_LOOKUP selects HAVE_CLK and COMMON_CLK selects CLKDEV_LOOKUP. So
> all symbols that select at least two of these symbols can be simplified.
>
> For imx, omap2 and ux500 some rearrangements were necessary before the
> simplification.
>
> Signed-off-by: U
* Uwe Kleine-König [130924 10:50]:
> CLKDEV_LOOKUP selects HAVE_CLK and COMMON_CLK selects CLKDEV_LOOKUP. So
> all symbols that select at least two of these symbols can be simplified.
>
> For imx, omap2 and ux500 some rearrangements were necessary before the
> simplification.
>
> Signed-off-by:
>
> This patch
> - updates DT binding for selection of ecc-scheme
> - updates DT binding for detection of ELM h/w engine
> - removes following obselete ECC schemes
> OMAP_ECC_HAMMING_CODE_DEFAULT (S/W based 1-bit Hamming
> ECC)
> OMAP_ECC_HAMMING_CODE_HW_ROMCODE (H/W based 1-bit
> Ham
On Tuesday 24 September 2013 01:08 PM, Will Deacon wrote:
> Hi Santosh,
>
> On Tue, Aug 13, 2013 at 02:31:04PM +0100, Santosh Shilimkar wrote:
>> On Tuesday 13 August 2013 07:19 AM, Will Deacon wrote:
>>> On Mon, Aug 12, 2013 at 07:34:13PM +0100, Santosh Shilimkar wrote:
On Friday 02 August 2
CLKDEV_LOOKUP selects HAVE_CLK and COMMON_CLK selects CLKDEV_LOOKUP. So
all symbols that select at least two of these symbols can be simplified.
For imx, omap2 and ux500 some rearrangements were necessary before the
simplification.
Signed-off-by: Uwe Kleine-König
---
arch/arm/Kconfig
Hi Santosh,
On Tue, Aug 13, 2013 at 02:31:04PM +0100, Santosh Shilimkar wrote:
> On Tuesday 13 August 2013 07:19 AM, Will Deacon wrote:
> > On Mon, Aug 12, 2013 at 07:34:13PM +0100, Santosh Shilimkar wrote:
> >> On Friday 02 August 2013 11:48 AM, Will Deacon wrote:
> >>> I think this an A9-specifi
On Monday 23 September 2013 22:47:15 Sebastian Reichel wrote:
> On Mon, Sep 23, 2013 at 10:06:46PM +0200, Pali Rohár wrote:
> > On Monday 23 September 2013 22:00:09 Sebastian Reichel wrote:
> > > On Mon, Sep 23, 2013 at 09:16:18PM +0200, Pali Rohár wrote:
> > > > It is not as simple as it looks. Th
From: Fabien Parent
Add the ability to specify constraints on the parents of a node.
Add as well seven test files for this feature.
node {
compatible = "abcomp";
abc = "abc";
subnode {
compatible = "comp";
abc = "def";
};
};
The schema below tests whether 'subno
From: Fabien Parent
Introduce a couple of real schema for OMAP DTS files. For the moment validate
only: MPU, DSP, INTC, IVA, TIME and COUNTER.
Signed-off-by: Fabien Parent
Signed-off-by: Benoit Cousson
---
bindings/arm/omap/counter.schema | 28 +
bindings/arm/omap/dsp.schema | 1
From: Fabien Parent
Add the ability to check whether a property has a given value or not.
Add as well 7 test files for this feature.
abc {
prop1 = <0 1 2 3>;
prop2 = "value0", "value1", "value3";
};
To check whether an integer array contains value from a given range
use the followin
From: Fabien Parent
Add constraints on array size:
- length: specify the exact length that an array must have.
- min-length: specify the minimum number of elements an array must have.
- max-length: specify the maximum number of elements an array must have.
Add as well four test files
From: Fabien Parent
The parser was not keeping enough information to allow a good error reporting.
Source Location information has been added inside a property instance to be
able to precisely tell where an error happened when a property does not match
its constraints as specified inside a schema
From: Fabien Parent
Add the ability to check if a node has some required children nodes.
Add as well two test files for this feature.
node {
compatible = "comp";
subnode1 {
};
subnode2 {
};
abc {
};
};
One can check if 'node' has the following subnode 'subnode1',
From: Fabien Parent
Add the ability to specify inside a schema that a property is required to be
present in the validated node. By default a property can be missing but one can
require its presence inside a node via the 'is-required' property.
Add as well two test files for this feature.
timer1
From: Fabien Parent
Add the path of the bindings schema directory on the command line used
for compiling the dts files. The dts files will be validated against all the
matching schemas found.
Signed-off-by: Fabien Parent
Signed-off-by: Benoit Cousson
---
scripts/Makefile.lib | 1 +
1 file cha
From: Fabien Parent
Add the ability to check if a property has the correct type. Right now dtc only
handles the two trivial types: integer array, string array. Since at the end
everything is an array of byte which may or may not be terminated by a null
byte this was enough.
A nice thing to add f
From: Fabien Parent
Add the possibility to specify in a schema a count limit for the nodes matching
the schema:
- count: if there is a match between a dts and a schema then there must
be exactly X match between the dts and the schema at the end of the
validation process.
- max-cou
From: Fabien Parent
Sometimes one may want a property to be required but the property could be
defined in a particular node or it could be defined in any of its parents node.
The concept of property inheritence has been added to fill this need. One can
specify that a property must be present in a
From: Fabien Parent
The verbose option '-B' will show additional messages in addition
to all validation errors. Right now the level 0 prints every nodes
which don't have at least one schema associated to it. Level 1
prints every properties which were not validated due to missing
constraints.
Acti
From: Fabien Parent
Add the infrastructure for dts validation through schema. The code build
an index of all the schemas found in a path given by the user on the
command line. This index will be used for the validation of a dts, it will be
used to know if a schema exists for a particular node and
From: Fabien Parent
There are a few memory leaks in dtc which until now were not that important
since they were all in the parser and only one instance of the parser was run
per instance of dtc. The following commits will add a validation of dts through
schema which have the same syntax as dts, i
From: Fabien Parent
Add support to navigate through the device tree and try to validate each node
which has an associated schema in the schema index. So far, only the framework
is added and no validation is really done yet.
Signed-off-by: Fabien Parent
Signed-off-by: Benoit Cousson
---
script
Hi All,
Following the discussion that happened during LCE-2013 and the email
thread started by Tomasz few months ago [1], here is a first attempt
to introduce:
- a schema language to define the bindings accurately
- DTS validation during device tree compilation in DTC itself
[1] http://www.spinic
* Pavel Machek [130923 17:23]:
> Hi!
>
> > > Tony, if you did not have time for review this patch months ago
> > > or you found it only today - no problem, I understand it. But
> > > what I need to know is what will happen with board-rx51-* files
> > > (and when?) You can see that DT does not
* Santosh Shilimkar [130924 08:56]:
> On Tuesday 24 September 2013 11:45 AM, Balaji T K wrote:
> > On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
> >> * Javier Martinez Canillas [130924
> >> 01:06]:
> >>> The OMAP GPIO controller HW requires a pin to be configured in GPIO
> >>> inpu
* Balaji T K [130924 08:54]:
> On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
> >
> >Also please mention the regression that this fixes. So far we know
> >that smsc911x for tobi and igep boards in mainline, and also the
>
> >MMC card detect for omap4 boards.
> Hi Tony,
>
> Card dete
On Tuesday 24 September 2013 11:45 AM, Balaji T K wrote:
> On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
>> * Javier Martinez Canillas [130924 01:06]:
>>> The OMAP GPIO controller HW requires a pin to be configured in GPIO
>>> input mode in order to operate as an interrupt input. Sin
On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
* Javier Martinez Canillas [130924 01:06]:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also
On 09/24/2013 05:40 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas [130924 01:06]:
>> The OMAP GPIO controller HW requires a pin to be configured in GPIO
>> input mode in order to operate as an interrupt input. Since drivers
>> should not be aware of whether an interrupt pin is also a GPIO
Dear,
after the inclusion of 851320e:
ARM: dts: Fix muxing and regulator for wl12xx on the SDIO bus for pandaboard
wlan0 is back on my pandaes, but it doesn't work and my logs are swamped
with:
[ 56.255401] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[ 56.264
* Javier Martinez Canillas [130924 01:06]:
> The OMAP GPIO controller HW requires a pin to be configured in GPIO
> input mode in order to operate as an interrupt input. Since drivers
> should not be aware of whether an interrupt pin is also a GPIO or not,
> the HW should be fully configured/enable
* Javier Martinez Canillas [130923 22:49]:
> On 09/23/2013 10:15 PM, Linus Walleij wrote:
> > wrote:
> > - When a second caller calls omap_gpio_request() it should
> > be OK as well, but only if the flags corresponds to the
> > previously enabled input mode. Else it should be
> > disallowed
From: Mugunthan V N
Date: Sat, 21 Sep 2013 00:50:37 +0530
> This patch series adds the support for configuring GMII_SEL register
> of control module to select the phy mode type and also to configure
> the clock source for RMII phy mode whether to use internal clock or
> the external clock from th
Rob Landley writes:
> On 09/23/2013 06:59:17 PM, Pavel Machek wrote:
>> During 3.12-rc, Will Deacon introduced code into arch/arm that
>> requires binutils 2.22.
>
> Um, my toolchain is using the last gplv2 snapshot of binutils out of
> git, which is just past 2.17 and can build armv7 (but not
+ Sekhar
Hi Balaji,
On 26/08/2013 15:53, Balaji T K wrote:
Add mmc2 dt node to dra7-evm board
and model eMMC vcc as fixed regulator.
Signed-off-by: Balaji T K
---
arch/arm/boot/dts/dra7-evm.dts | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/arm/
Hi Aaro,
On 21/09/2013 01:40, Aaro Koskinen wrote:
"gpmc,sync-clki-ps" is not defined/documented, it should be
"gpmc,sync-clk-ps" instead.
Thanks for the fix. I've just applied it with a slight change in the
subject for consistency:
ARM: dts: omap3-devkit8000: fix a typo in GMPC node
Regar
Modelling the RESET line as a regulator supply wasn't a good idea
as it kind of abuses the regulator framework and also makes adaptation
code more complex.
Instead, manage the RESET gpio line directly in the driver. Update
the device tree binding information.
This also makes us easy to migrate to
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/usb-host.c | 11 +--
1 files changed, 1 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-omap2/usb-
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap5-uevm.dts | 26 ++
1 files changed, 2 insertions(+), 24 deletions(-)
diff --git a/arch/arm/boot
Hi,
Modelling the RESET line as a regulator supply wasn't a good idea
as it abuses the regulator framework and makes adaptation
code/data more complex.
Instead, manage the RESET gpio line directly in the driver.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it
On Tue, Sep 24, 2013 at 05:14:46PM +0900, Simon Horman wrote:
> [ Cc: Olof Johansson, Kevin Hilman and Arnd Bergman: arm-soc maintainers ]
>
> On Mon, Sep 23, 2013 at 11:40:57PM +0200, Thierry Reding wrote:
> > This series adds the ability to specify a GPIO and a power supply to
> > enable a backl
Use a common naming scheme "mode0name.modename flags" for the
USB host pins to be consistent.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts | 24
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +-
1 files changed, 1 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boo
Add information about the USB OTG PHY. Without this
the OTG port on beagle will not work.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/oma
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/board-omap3beagle.c |6 --
arch/a
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by
The GPIO number of the RESET line can be passed to the
driver using the gpio_reset member.
Signed-off-by: Roger Quadros
---
include/linux/usb/usb_phy_gen_xceiv.h |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/include/linux/usb/usb_phy_gen_xceiv.h
b/include/linux/usb/
Hi,
Can you assist me to invest funds in your Country? if yes, then get back to
me, so I can give you details and areas you can participate by being my
partner.
Ms. Sarah
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel
On Tuesday 24 September 2013 01:24 PM, Javier Martinez Canillas wrote:
> On 09/24/2013 09:39 AM, Sricharan R wrote:
>> Hi,
>> On Monday 23 September 2013 10:37 PM, Tony Lindgren wrote:
>>> * Javier Martinez Canillas [130923 10:09]:
On 09/23/2013 06:45 PM, Tony Lindgren wrote:
> Hmm does t
[ Cc: Olof Johansson, Kevin Hilman and Arnd Bergman: arm-soc maintainers ]
On Mon, Sep 23, 2013 at 11:40:57PM +0200, Thierry Reding wrote:
> This series adds the ability to specify a GPIO and a power supply to
> enable a backlight.
>
> Patch 1 refactors the power on and power off sequences into s
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW should be fully configured/enabled as an IRQ if a driver solely
uses IRQ APIs such as
On 09/24/2013 09:39 AM, Sricharan R wrote:
> Hi,
> On Monday 23 September 2013 10:37 PM, Tony Lindgren wrote:
>> * Javier Martinez Canillas [130923 10:09]:
>>> On 09/23/2013 06:45 PM, Tony Lindgren wrote:
Hmm does this still work for legacy platform data based
drivers that are doing gpio
Hi,
On Monday 23 September 2013 10:37 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas [130923 10:09]:
>> On 09/23/2013 06:45 PM, Tony Lindgren wrote:
>>> Hmm does this still work for legacy platform data based
>>> drivers that are doing gpio_request() first?
>>>
>> Yes it still work when boo
This patch disables devices initially(status = "disabled").
Devices will only be probed, if the devices are
present in the board file(status = "okay").
Signed-off-by: Sourav Poddar
---
v1->v2:
change approach to disabling devices in dtsi and
enable it in respective board file.
arch/arm/boot/dts/
81 matches
Mail list logo
