Rob Herring in devicetree/msg06598.html
> This is interesting approach using the dts syntax,
Benoit Cousson in devicetree/msg06617.html
> it has the big advantage of re-using the parser already included in DTC for
> free. In term or readability, it avoids to re-defining a brand new syntax for
> pe
[RandText,uborka-text: Specified TextBlock does not exists!]
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: "Mark A. Greer"
Add the generic AM33XX AES module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing the data
for the AES module.
[jo...@ti.com: Dropped interrupt-parent propert, documentation fixups]
CC: P
From: "Mark A. Greer"
Add the generic AM33XX SHAM module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing the data
for the SHAM module.
[jo...@ti.com: Dropped interrupt-parrent property, documentation fixups]
CC
AES interrupts were previously not used, but after recent changes to omap-aes
driver, its being used. We correct the interrupt number to have working PIO
mode.
Signed-off-by: Joel Fernandes
---
arch/arm/boot/dts/am33xx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch
These patches are some minor fixups and changes to commit messages to the
AM33XX crypto (aes, sham) patches with reference to the comments at:
http://comments.gmane.org/gmane.linux.drivers.devicetree/45961
Joel Fernandes (1):
ARM: dts: AM33XX: Fix AES interrupt number
Mark A. Greer (2):
ARM:
These patches were not authored by me but I'll go ahead and fix them up anyway.
On 10/04/2013 09:33 AM, Mark Rutland wrote:
> On Mon, Sep 30, 2013 at 04:13:01PM +0100, Joel Fernandes wrote:
>> From: "Mark A. Greer"
>>
>> Add the generic AM33XX AES module's device tree data and
>> enable it for th
On 10/04/2013 09:26 AM, Mark Rutland wrote:
> On Mon, Sep 30, 2013 at 04:13:00PM +0100, Joel Fernandes wrote:
>> From: "Mark A. Greer"
>>
>> Add the generic AM33XX SHAM module's device tree data and
>> enable it for the am335x-evm, am335x-evmsk, and am335x-bone
>> platforms. Also add Documentatio
The am335x can't detect pending cirq in PM runtime suspend.
This patch reconfigures dat1 as a GPIO before going to suspend.
SDIO interrupts are detected with the GPIO, while in runtime
suspend, standard detection of the module block otherwise.
Signed-off-by: Andreas Fenkart
diff --git a/Document
From: Tony Lindgren
We want to get rid of the omap specific platform init code
callbacks as they don't play nice with device tree.
Let's convert the context loss check to be based on a
register state detection instead.
Cc: Andreas Fenkart
Cc: Balaji T K
Signed-off-by: Tony Lindgren
diff --g
Update the debugfs related code for the SDIO IRQ support.
Note that PSTATE shows current state of data lines, incl.
SDIO IRQ pending
Signed-off-by: Andreas Fenkart
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index a8894ee..f7fe06f 100644
--- a/drivers/mmc/host/omap
For now, only support SDIO interrupt if we are booted with
DT. This is because some platforms need special quirks. And
we don't want to add new legacy mux platform init code
callbacks any longer as we are moving to DT based booting
anyways.
Broken hardware, missing the swakueup line, should fallba
Changes:
- split the subject patch into normal handling and
workaround for am335x
- rebase
Andreas Fenkart (3):
mmc: omap_hsmmc: Enable SDIO IRQ.
mmc: omap_hsmmc: Remux pins to support SDIO interrupt on AM335x
mmc: omap_hsmmc: debugfs for SDIO IRQ and GPIO remux
Tony Lindgren (1):
mmc:
13 matches
Mail list logo
