Hi,
On Fri, 2013-07-26 at 02:06 +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, July 25, 2013 1:52 PM
On Thu, Jul 25, 2013 at 07:46:58PM +, Paul Zimmerman wrote:
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index
Add support for the OMAP5 version of the SHAM module
that is present on OMAP5 and AM43xx SoCs.
This module is very simialar to OMAP4 version of SHAM module,
and adds SHA384 SHA512 hardware-accelerated hash functions to it.
To handle the higher digest size of SHA512, few SHA512_DIGEST_i
(i=1-16,
This patch series adds support for SHA348 and SHA512 in addition to MD5,
SHA1, SHA224 SHA256 that the omap sha module supports. Also adding the pdata
for OMAP5 and AM43xx Soc's.
And using devm_* calls to make cleanup paths simpler.
Lokesh Vutla (4):
crypto: omap-sham: Add SHA384 and SHA512
Using devm_request_irq() rather than request_irq().
So removing free_irq() calls from the probe error
path and the remove handler.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/omap-sham.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/omap-sham.c | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index b82b140..ae1ca8b2
Adding support for SHA348 and SHA512 in addition to MD5, SHA1, SHA224
SHA256 that the omap sha module supports.
In order to add the support
- Removed hard coded register offsets and passing offsets from pdata
- Updating Flag offsets so that they can be used for SHA256 and SHA512
- Adding the algo
Panda's DVI connector's DDC pins are connected to OMAP's third i2c bus.
With non-DT, the bus number was 3, and that is what is used in the
dss-common.c which contains the platform data for Panda's DVI.
However, with DT, the bus number is 2. As we now only have DT boot for
Panda, we have to change
Hi,
The display drivers for new OMAP DSS driver model were merged in v3.11, but the
board files were not changed to use them. This series changes the board files
to take those new drivers into use.
There's mostly nothing special in the patches. One complication is with Overo
board file, which
Add some of the most common new display drivers to omap2plus_defconfig
to be built as modules.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/configs/omap2plus_defconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/configs/omap2plus_defconfig
Use new display drivers for AM3517EVM board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Note: the management of LCD GPIOs is unclear. They were originally muxed
as inputs, and LCD_PANEL_PWR was labelled
Use new display drivers for OMAP3 Stalker board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-omap3stalker.c | 61
Use new display drivers for LDP board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-ldp.c | 68
Use new display drivers for cm-t35 board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-cm-t35.c | 100
Use new display drivers for devkit8000 board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-devkit8000.c | 96
Use the new display drivers for OMAP4 Panda and OMAP4 SDP boards.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/dss-common.c |
Use new display drivers for H4 board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-h4.c | 48
Use new display drivers for 2430SDP board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-2430sdp.c | 57
Use the new display drivers for RX51 board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
Tested-by: Aaro Koskinen aaro.koski...@iki.fi
---
Use the new display drivers for Beagleboard.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 56
The old display drivers are no longer used, and will be phased out. So
remove them from the omap2plus_defconfig.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/configs/omap2plus_defconfig | 7 ---
1 file changed, 7 deletions(-)
diff --git
Use new display drivers for Zoom board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-zoom-display.c | 30
This is no longer needed as omap4 is now booted using device tree.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/dss-common.c | 47
arch/arm/mach-omap2/dss-common.h | 2 --
2 files changed, 49 deletions(-)
diff --git
4430SDP board has an option for a PicoDLP mini-projector. PicoDLP cannot
be used at the same time as the second LCD, and there are GPIOs that
need to be set/unset when changing the used display.
Managing that kind of board specific setup is not simple without board
file callbacks. As only some
Use the new display drivers for OMAP3 Overo board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Note that the LCD add-on boards for lcd43 and lcd35 use the same GPIOs
for the panels. This means that both
Use new display drivers for igep0020 board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-igep0020.c | 36
Use new display drivers for OMAP3 Pandora board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
Tested-by: Grazvydas Ignotas nota...@gmail.com
---
Use new display drivers for 3430SDP board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 83
Use new display drivers for OMAP3EVM board.
The new OMAP display drivers were merged for 3.11, and we can now change
the board files to use the new ones and phase out the old ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-omap3evm.c | 87
On 07/26/2013 05:00 AM, Joel Fernandes wrote:
On 07/25/2013 09:49 PM, Joel Fernandes wrote:
[..]
Can I get back on this topic. When USB and ethernet was working for me
as stated above, I was not doing tftpboot. When I use tftpboot the
images are obtained from the tftp server, but after kernel
On 07/25/2013 08:28 PM, Felipe Balbi wrote:
On Thu, Jul 18, 2013 at 11:53:05AM +0300, Roger Quadros wrote:
Till now we were modelling the RESET line as a voltage regulator and
using the regulator framework to manage it.
[1] introduces a GPIO based reset controller driver. We use that
to
After the platform devices are created using PLATFORM_DEVID_AUTO, the
device names given in usb_bind_phy (in board file) does not match with
the actual device name causing the USB PHY library not to return the
PHY reference when the MUSB controller request for the PHY in the non-dt boot
case.
So
After the platform devices are created using PLATFORM_DEVID_AUTO, the
device names given in usb_bind_phy (in board file) does not match with
the actual device name causing the USB PHY library not to return the
PHY reference when the MUSB controller request for the PHY in the non-dt boot
case.
So
Previously MUSB wrapper (OMAP) device used PLATFORM_DEVID_AUTO while creating
MUSB core device. So in usb_bind_phy (binds the controller with the PHY), the
device name of the controller had *.auto* in it. Since with using
PLATFORM_DEVID_AUTO, there is no way to know the exact device name in
Hi,
the commit:
commit 09fc7d22b024692b2fe8a943b246de1af307132b
Author: Felipe Balbi ba...@ti.com
Date: Wed Apr 24 17:21:42 2013 +0300
usb: musb: fix incorrect usage of resource pointer
We can't simply pass the resource pointer from our
device down to our children, otherwise
Hi,
On Fri, Jul 26, 2013 at 09:48:26AM +0300, Ivan T. Ivanov wrote:
Also, this is not *modifying* what was passed, just skipping the xHCI
address space so we don't request_mem_region() an area we won't really
handle and prevent xhci-hcd.ko from probing.
Hmm? platform_get_resource()
On 07/26/2013 12:13 PM, Arend van Spriel wrote:
On 07/26/2013 05:00 AM, Joel Fernandes wrote:
On 07/25/2013 09:49 PM, Joel Fernandes wrote:
[..]
Can I get back on this topic. When USB and ethernet was working for me
as stated above, I was not doing tftpboot. When I use tftpboot the
images
On Fri, Jul 26, 2013 at 07:14:45PM +1000, NeilBrown wrote:
Hi,
the commit:
commit 09fc7d22b024692b2fe8a943b246de1af307132b
Author: Felipe Balbi ba...@ti.com
Date: Wed Apr 24 17:21:42 2013 +0300
usb: musb: fix incorrect usage of resource pointer
We can't simply pass
On 07/26/2013 12:15 PM, Arend van Spriel wrote:
On 07/26/2013 12:13 PM, Arend van Spriel wrote:
On 07/26/2013 05:00 AM, Joel Fernandes wrote:
On 07/25/2013 09:49 PM, Joel Fernandes wrote:
[..]
Can I get back on this topic. When USB and ethernet was working for me
as stated above, I was not
On 07/26/2013 01:23 PM, Arend van Spriel wrote:
On 07/26/2013 12:15 PM, Arend van Spriel wrote:
On 07/26/2013 12:13 PM, Arend van Spriel wrote:
On 07/26/2013 05:00 AM, Joel Fernandes wrote:
On 07/25/2013 09:49 PM, Joel Fernandes wrote:
[..]
Can I get back on this topic. When USB and
On 07/26/2013 12:37 PM, Roger Quadros wrote:
On 07/26/2013 01:23 PM, Arend van Spriel wrote:
On 07/26/2013 12:15 PM, Arend van Spriel wrote:
On 07/26/2013 12:13 PM, Arend van Spriel wrote:
On 07/26/2013 05:00 AM, Joel Fernandes wrote:
On 07/25/2013 09:49 PM, Joel Fernandes wrote:
[..]
Can
On Fri, 26 Jul 2013 13:20:08 +0300 Felipe Balbi ba...@ti.com wrote:
On Fri, Jul 26, 2013 at 07:14:45PM +1000, NeilBrown wrote:
Hi,
the commit:
commit 09fc7d22b024692b2fe8a943b246de1af307132b
Author: Felipe Balbi ba...@ti.com
Date: Wed Apr 24 17:21:42 2013 +0300
usb:
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
drivers/phy/phy-omap-usb2.c |
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed. Also twl4030-usb driver is moved
to
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed. Also twl4030-usb driver is moved
to
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
drivers/phy/phy-omap-usb2.c |
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
Resending with fixed device tree mailing address!
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that
On Fri, Jul 26, 2013 at 10:24:58PM +1000, NeilBrown wrote:
On Fri, 26 Jul 2013 13:20:08 +0300 Felipe Balbi ba...@ti.com wrote:
On Fri, Jul 26, 2013 at 07:14:45PM +1000, NeilBrown wrote:
Hi,
the commit:
commit 09fc7d22b024692b2fe8a943b246de1af307132b
Author: Felipe Balbi
This patchset adds wake up capability for the keypad and
workaround for i689 errata.
Based on top of v3.11-rc2
Depends on:
Input: omap-keypad: Convert to threaded IRQ
https://patchwork.kernel.org/patch/2832920/
Input: omap-keypad: Cleanup - use bitfiled instead of hardcoded values
From: Axel Haslam axelhas...@ti.com
Set debounce time value to 12ms to workaround the errata.
ERRATA DESCRIPTION:
When a key is released for a time shorter than the debounce time,
in-between 2 key press (KP1 and KP2), the keyboard state machine will go to
idle mode and will never detect the key
From: Axel Haslam axelhas...@ti.com
Set mpu irq to level instead of edge, since if mpu is in low power
an edge detection may be lost if the event is a wkup event.
Signed-off-by: Axel Haslam axelhas...@ti.com
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
---
Based on top of v3.11-rc2
Enable/disable IRQ wake in suspend/resume handlers
to make the keypad wakeup capable.
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
---
drivers/input/keyboard/omap4-keypad.c | 38 +
1 file changed, 38 insertions(+)
diff --git
Sorry,
this patch is incomplete and was sent by mistake.
I will sent v2
On 07/26/2013 07:29 PM, Illia Smyrnov wrote:
Enable/disable IRQ wake in suspend/resume handlers
to make the keypad wakeup capable.
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
---
From: Axel Haslam axelhas...@ti.com
Set mpu irq to level instead of edge, since if mpu is in low power
an edge detection may be lost if the event is a wkup event.
Signed-off-by: Axel Haslam axelhas...@ti.com
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
---
Based on top of v3.11-rc2
This patchset adds wake up capability for the keypad and
workaround for i689 errata.
Based on top of v3.11-rc2
Depends on:
Input: omap-keypad: Convert to threaded IRQ
https://patchwork.kernel.org/patch/2832920/
Input: omap-keypad: Cleanup - use bitfiled instead of hardcoded values
From: Axel Haslam axelhas...@ti.com
Set debounce time value to 12ms to workaround the errata.
ERRATA DESCRIPTION:
When a key is released for a time shorter than the debounce time,
in-between 2 key press (KP1 and KP2), the keyboard state machine will go to
idle mode and will never detect the key
Enable/disable IRQ wake in suspend/resume handlers
to make the keypad wakeup capable.
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
---
drivers/input/keyboard/omap4-keypad.c | 43 +
1 file changed, 43 insertions(+)
diff --git
Since, qspi controller uses quad read.
Configuring the command register, if the transfer of data needs
dual or quad lines.
This patch has been done on top of the following patch[1], which is the
basic idea of adding dual/quad support in spi framework.
$subject patch will undergo changes with the
This patch series add support for ti qspi controller.
The previous version link is here:
https://lkml.org/lkml/2013/7/18/154
patch 1 of the previous version already picked.
Resending other two with comments fixed.
Sourav Poddar (2):
drivers: spi: Add qspi flash controller
driver: spi: Add
The patch add basic support for the quad spi controller.
QSPI is a kind of spi module that allows single,
dual and quad read access to external spi devices. The module
has a memory mapped interface which provide direct interface
for accessing data form external spi devices.
The patch will
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, July 26, 2013 2:54 AM
Also, this is not *modifying* what was passed, just skipping the xHCI
address space so we don't request_mem_region() an area we won't really
handle and prevent xhci-hcd.ko from probing.
Hmm?
Hi Sergei
On Mon, 22 Jul 2013, Sergei Shtylyov wrote:
Perhaps it's better to follow what Documentation/SubmittingPatches
suggests:
#else
static inline __init void omap3_evm_display_init(void) {}
...
... and eliminate #ifdef here?
While I agree with you in principle, the original
Hi,
On Fri, Jul 26, 2013 at 06:44:23PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, July 26, 2013 2:54 AM
Also, this is not *modifying* what was passed, just skipping the xHCI
address space so we don't request_mem_region() an area we won't
Small typo fix. Received ack from mfd already.
Awaiting acks from all the rest.
As Lee from mfd stated, we can remove these during staging now.
or we'll have to leave typos as is later on.
Zubair Lutfullah (1):
mfd: input: arm: dts: doc: ti_am335x: typo fixes (coordiante -
coordinate)
Did a grep for 'coordiante' and replaced them all with 'coordinate'
Signed-off-by: Zubair Lutfullah zubair.lutful...@gmail.com
Acked-by: Lee Jones lee.jo...@linaro.org
---
.../bindings/input/touchscreen/ti-tsc-adc.txt |4 ++--
arch/arm/boot/dts/am335x-evm.dts |2 +-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, July 26, 2013 1:32 PM
On Fri, Jul 26, 2013 at 06:44:23PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, July 26, 2013 2:54 AM
Also, this is not *modifying* what was passed, just skipping
On Fri, 26 Jul 2013 16:51:08 +0300 Felipe Balbi ba...@ti.com wrote:
On Fri, Jul 26, 2013 at 10:24:58PM +1000, NeilBrown wrote:
On Fri, 26 Jul 2013 13:20:08 +0300 Felipe Balbi ba...@ti.com wrote:
On Fri, Jul 26, 2013 at 07:14:45PM +1000, NeilBrown wrote:
Hi,
the commit:
Having worked out how to get around the MMC ordering issue without having
to go and re-tweak it should it change again in the future, I've added
the SDP back into the build.
On Thu, Jul 25, 2013 at 09:50:13AM +0300, Tomi Valkeinen wrote:
On 25/07/13 09:40, Tomi Valkeinen wrote:
On 24/07/13
On Fri, Jul 12, 2013 at 03:11:46PM +0300, Felipe Balbi wrote:
hi,
On Fri, Jul 12, 2013 at 02:55:42PM +0300, Grygorii Strashko wrote:
Since commit a630fbf serial: omap: Fix device tree based PM runtime
the OMAP serial driver will always try to restore its context in
On Wed, Jul 17, 2013 at 5:40 PM, Tony Lindgren t...@atomide.com wrote:
* Grygorii Strashko grygorii.stras...@ti.com [130717 04:49]:
The pinctrl support in Device core assumed to be optional - so, It's
valid case, when there are no definition for default device's pinctrl
states in DT at all
Tonight I put on a Jon Hopkins album, in recollection of my UK ARM Linux
colleagues perhaps, and started testing, and eventually wound up with this
one:
commit 621a0147d5c921f4cc33636ccd0602ad5d7cbfbc
Author: Will Deacon will.dea...@arm.com
Date: Wed Jun 12 12:25:56 2013 +0100
ARM:
83 matches
Mail list logo
