Hi Grygorii,
On Monday 05 August 2013 05:14 PM, Grygorii Strashko wrote:
On 08/04/2013 07:27 PM, Rajendra Nayak wrote:
From: R Sricharan r.sricha...@ti.com
The DRA7xx is a high-performance, infotainment application device,
based on enhanced OMAP architecture integrated on a 28-nm technology.
Add the generic AM33xx RNG 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 RNG module.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
.../devicetree/bindings/hwrng/omap_rng.txt
Add clock data for RNG module on AM33xx SoC.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/cclock33xx_data.c |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/mach-omap2/cclock33xx_data.c
b/arch/arm/mach-omap2/cclock33xx_data.c
index ba6534d..865d30e
This patch series adds HWMOD, CLOCK and DT data for
RNG module.
Lokesh Vutla (3):
ARM: AM33XX: hwmod: Add rng module data
ARM: AM33xx: Add rng clock data
ARM: dts: AM33xx: Add RNG node
.../devicetree/bindings/hwrng/omap_rng.txt | 22
Add RNG hwmod data for AM33xx SoC.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 35
1 file changed, 35 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
On Tue, Aug 06, 2013 at 10:53:44AM +0300, Pantelis Antoniou wrote:
Removing any omap device always resulted in a crash; turns out
BUS_NOTIFY_DEL_DEVICE is not the last notifier event sent in the
course of removing the device, the correct event is
BUS_NOTIFY_UNBOUND_DRIVER, which still is not
On Tue, Aug 06, 2013 at 10:53:40AM +0300, Pantelis Antoniou wrote:
Platform device removal uncovered a number of problems with
the way resources are handled in the core platform code.
Resources now form child/parent linkages and this requires
proper linking of the resources. On top of that
Hi Greg,
On Aug 6, 2013, at 12:36 PM, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 10:53:40AM +0300, Pantelis Antoniou wrote:
Platform device removal uncovered a number of problems with
the way resources are handled in the core platform code.
Resources now form child/parent linkages
On Tue, Aug 06, 2013 at 12:37:25PM +0300, Pantelis Antoniou wrote:
I don't like this at all, sorry.
Don't shoot the messenger please...
This is all about fixing a crash without messing too many things.
I understand, it's not your fault at all.
And I was waiting for the day when
On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote:
Hi Greg,
On Aug 6, 2013, at 12:36 PM, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 10:53:40AM +0300, Pantelis Antoniou wrote:
Platform device removal uncovered a number of problems with
the way resources are
On Tue, Aug 06, 2013 at 06:15:27PM +0800, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote:
What would it take to move all this into driver core?
What specifically would you move into there?
A variable to hold the streaming dma_mask, so that its in
Hi Greg,
On Aug 6, 2013, at 1:15 PM, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote:
Hi Greg,
On Aug 6, 2013, at 12:36 PM, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 10:53:40AM +0300, Pantelis Antoniou wrote:
Platform device removal
Hi,
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
TYPE2 meaning has changed. It is now a USB2 phy with Power down bit in
control_dev_conf register.
Introduce TYPE3 and TYPE4 PHY. TYPE3 is USB3 phy with DPLL and individual
TX/RX power control. TYPE4 is USB2 phy with power aux
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use phandles to get the
reference to the control device.
As we don't
Hi,
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use phandles to get the
reference to the control device.
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use phandles to get the
reference to the control device.
As we don't
From: Ivan T. Ivanov iiva...@mm-sol.com
Hi,
These patches add basic support for USB3.0 controllers found on
MSM platforms. First patch add 2 USB PHY drivers and second one
add support for Qualcomm wrapper IP over DWC3 controller. Patches
are just skeletons, no power management.
DWC3 IP in
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
This function was preventing us from supporting multiple
instances. Get rid of it. Since we support DT boots only,
users can get the control device phandle from the DT node.
Signed-off-by: Roger Quadros rog...@ti.com
Tested-by: Kishon
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
.../devicetree/bindings/usb/msm-ssusb.txt | 39 +
drivers/usb/dwc3/Kconfig |8 +
drivers/usb/dwc3/Makefile |1 +
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
.../devicetree/bindings/usb/msm-ssusb.txt | 49 +++
drivers/usb/phy/Kconfig| 11 +
drivers/usb/phy/Makefile |2 +
On 08/06/2013 11:11 AM, Rajendra Nayak wrote:
Hi Grygorii,
On Monday 05 August 2013 05:14 PM, Grygorii Strashko wrote:
On 08/04/2013 07:27 PM, Rajendra Nayak wrote:
From: R Sricharan r.sricha...@ti.com
The DRA7xx is a high-performance, infotainment application device,
based on enhanced OMAP
On Tue, 2013-08-06 at 12:53 +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
I am sure that the information in the subject is more than enough for
you, but would you care to give some more background for the commit log?
On Tue, 2013-08-06 at 12:53 +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
The same comment as for the RFC 1/2 here...
.../devicetree/bindings/usb/msm-ssusb.txt | 39 +
drivers/usb/dwc3/Kconfig
Dear All,
We are working on omap4470 based device,kernel-3.0.31 is running on this.
In our device modem is connected to OMAP4470 using USB EHCI.
In our current kernel code, clocks are enabled when ports get connected
and disabled during disconnect.Due to this current consumption is
On 08/06/2013 02:51 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use
On 08/06/2013 02:45 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 01 August 2013 07:35 PM, Roger Quadros wrote:
TYPE2 meaning has changed. It is now a USB2 phy with Power down bit in
control_dev_conf register.
Introduce TYPE3 and TYPE4 PHY. TYPE3 is USB3 phy with DPLL and individual
Hi,
On Tue, 2013-08-06 at 13:12 +0100, Pawel Moll wrote:
On Tue, 2013-08-06 at 12:53 +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
I am sure that the information in the subject is more than enough for
you, but
Am 06.08.2013 12:14, schrieb Greg Kroah-Hartman:
What exactly is a platform device anyway?
Originally it was a something that wasn't connected to a bus, but just
had memory-mapped i/o. Like the PS2 keyboard controller.
Embedded systems got ahold of this and went to town, and made
On Tue, 2013-08-06 at 13:21 +0100, Pawel Moll wrote:
On Tue, 2013-08-06 at 12:53 +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
The same comment as for the RFC 1/2 here...
Will fix this.
On Tue, Aug 06, 2013 at 06:25:32PM +0530, Bharathraj Nagaraju wrote:
Dear All,
We are working on omap4470 based device,kernel-3.0.31 is running on this.
Have you tried the 3.10 kernel for this? I think you might find that
this already is resolved there, as lots of pm USB work has
On Tue, Aug 06, 2013 at 12:53:10PM +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
.../devicetree/bindings/usb/msm-ssusb.txt | 49 +++
drivers/usb/phy/Kconfig| 11 +
On Sunday 04 August 2013 02:28 PM, Sourav Poddar wrote:
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
On Tue, Aug 06, 2013 at 12:53:11PM +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
What does the glue layer do? Is it an actual piece of hardware, or
just some platform-specific code?
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
Hi,
On 08/06/2013 03:55 PM, Bharathraj Nagaraju wrote:
Dear All,
We are working on omap4470 based device,kernel-3.0.31 is running on this.
In our device modem is connected to OMAP4470 using USB EHCI.
In our current kernel code, clocks are enabled when ports get connected
and
Hi,
On Tue, 2013-08-06 at 15:03 +0100, Mark Rutland wrote:
On Tue, Aug 06, 2013 at 12:53:10PM +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
.../devicetree/bindings/usb/msm-ssusb.txt | 49 +++
Hi,
On Tue, 2013-08-06 at 15:07 +0100, Mark Rutland wrote:
On Tue, Aug 06, 2013 at 12:53:11PM +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
What does the glue layer do? Is it an actual piece of hardware, or
just some platform-specific code?
It is hardware layer
On Tue, 2013-08-06 at 14:46 +0100, Ivan T. Ivanov wrote:
+ reg = 0xf920 0xcd00;
+ interrupts = 0 131 0;
+ interrupt-names = irq;
+ usb-phy = dwc3_usb2, dwc3_usb3;
+ tx-fifo-resize;
+ };
From: Andy Green andy.gr...@linaro.org
You might have CONFIG_PM, but you might not have CONFIG_SUSPEND, in which
case these are unused.
Signed-off-by: Andy Green andy.gr...@linaro.org
Signed-off-by: Mark Brown broo...@linaro.org
---
drivers/usb/dwc3/dwc3-pci.c | 2 +-
1 file changed, 1
From: Daniel Mack zon...@gmail.com
Commit b7e2e75a8c (usb: gadget: drop unused USB_GADGET_MUSB_HDRC)
dropped a config symbol that was unused by the musb core, but it turns
out that board support code still had references to it.
As the core now handles both dual role and host-only modes, we can
Hi,
USB subsystem changes broke the USB peripheral/gadget on N800, N810 and
RX-51/N900 during the merge window. We need to fix this in board files. I
tested all these with 3.11-rc4 + g_ether + ssh.
Aaro Koskinen (1):
ARM: OMAP: rx51: change musb mode to OTG
Daniel Mack (1):
ARM: omap2: fix
Peripheral-only mode got broken in v3.11-rc1 because of unknown reasons.
Change the mode to OTG, in practice that should work equally well even
when/if the regression gets fixed.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
---
arch/arm/mach-omap2/board-rx51.c | 2 +-
1 file changed, 1
From: Vaibhav Bedia vaibhav.be...@ti.com
Needed to let the AM335x PM handle the IPs which need forced
standby transition during every suspend-resume cycle when
the corresponding driver is not compiled into the kernel.
Signed-off-by: Vaibhav Bedia vaibhav.be...@ti.com
Signed-off-by: Dave Gerlach
From: Vaibhav Bedia vaibhav.be...@ti.com
Allow interrupt for wkup_m3 to be set from DT.
Signed-off-by: Vaibhav Bedia vaibhav.be...@ti.com
Signed-off-by: Dave Gerlach d-gerl...@ti.com
Cc: Benoit Cousson benoit.cous...@linaro.org
---
arch/arm/boot/dts/am33xx.dtsi |1 +
1 file changed, 1
From: Vaibhav Bedia vaibhav.be...@ti.com
OMAP timer code registers two timers - one as clocksource
and one as clockevent. Since AM33XX has only one usable timer
in the WKUP domain one of the timers needs suspend-resume
support to restore the configuration to pre-suspend state.
commit adc78e6
From: Vaibhav Bedia vaibhav.be...@ti.com
Interacting with WKUP-M3 requires some more control
module register writes. Add the register offsets and
APIs to write to these.
Signed-off-by: Vaibhav Bedia vaibhav.be...@ti.com
Signed-off-by: Dave Gerlach d-gerl...@ti.com
---
Hi,
This is the third version of the patch series for adding basic suspend-resume
support for AM33XX, previously submitted by Vaibhav Bedia. This patchset
is based on 3.11-rc4 and depends on a forthcoming patchset from Suman Anna
that adds mailbox support for the wkup_m3. The patches at [1],
From: Vaibhav Bedia vaibhav.be...@ti.com
With all the requisite changes in place we can now
enable the basic PM support for AM335x. This patch
updates the various OMAP files to enable suspend-resume
on AM335x.
Signed-off-by: Vaibhav Bedia vaibhav.be...@ti.com
Signed-off-by: Dave Gerlach
From: Vaibhav Bedia vaibhav.be...@ti.com
SDRAM controller on AM33XX requires that a modification of certain
bit-fields in PWR_MGMT_CTRL register (ref. section 7.3.5.13 in
AM335x-Rev H) is followed by a dummy read access to SDRAM. This
scenario arises when entering a low power state like
From: Vaibhav Bedia vaibhav.be...@ti.com
In preparation for suspend-resume support for AM33XX, add
the assembly file with the code which is copied to internal
memory (OCMC RAM) during bootup and runs from there.
As part of the low power entry (DeepSleep0 mode in AM33XX TRM),
the code running
From: Vaibhav Bedia vaibhav.be...@ti.com
AM335x supports various low power modes as documented
in section 8.1.4.3 of the AM335x TRM which is available
@ http://www.ti.com/litv/pdf/spruh73f
DeepSleep0 mode offers the lowest power mode with limited
wakeup sources without a system reboot and is
OMAP4 and AM33XX share the same EMIF controller IP. Although there
are significant differences in the IP integration due to which
AM33XX can't reuse the EMIF driver DVFS similar to OMAP4,
it can definitely benefit by reusing the EMIF related macros
defined in drivers/memory/emif.h.
In the current
On Tue, 2013-08-06 at 16:15 +0100, Pawel Moll wrote:
On Tue, 2013-08-06 at 14:46 +0100, Ivan T. Ivanov wrote:
+ reg = 0xf920 0xcd00;
+ interrupts = 0 131 0;
+ interrupt-names = irq;
+
On Tue, Aug 6, 2013 at 1:33 AM, Lokesh Vutla lokeshvu...@ti.com wrote:
Add the generic AM33xx RNG 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 RNG module.
Signed-off-by: Lokesh
Hi,
This is an updated series for adding the device tree support to
the OMAP mailbox driver. The series is based on 3.11-rc4 and now
includes the support for AM335 WkupM3 mailbox.
The support for WkupM3 mailbox is essential for achieving the PM
Suspend on AM335 devices, and this series is a
Logic has been added to the OMAP2+ mailbox code to
parse the mailbox dt nodes and construct the different
mailboxes associated with the instance. The design is
based on gathering the same information that was being
passed previously through the platform data, except for
the interrupt type
A new structure, omap_mbox_device, is added to contain
the global variables pertinent to a mailbox h/w IP block.
This enables the support for having multiple instances of
the same h/w IP block in the SoC. The startup sequence for
each mailbox is also simplified along the way, removing the
usage of
Add the hwmod data for the mailbox IP in OMAP5 SoC.
This is needed to be able to enable the OMAP mailbox
support for OMAP5.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 42 ++
1 file changed, 42 insertions(+)
diff --git
The mailbox DT node data has been added for OMAP2420,
OMAP2430, OMAP3430/OMAP3630, OMAP44xx devices. Data
for OMAP5 and other SoCs will be added separately.
The mailbox static device initialization logic is also
adjusted for a DT boot.
Signed-off-by: Suman Anna s-a...@ti.com
---
The type definition omap_mbox_type_t used for distinguishing
OMAP1 from OMAP2+ mailboxes does not really belong to the
ops, and has been cleaned up.
Signed-off-by: Loic Pallardy loic.palla...@st.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap1.c | 27
The WkupM3 mailbox used for triggering PM operations such as suspend
and resume on AM33x/AM43x is special in that the M3 processor cannot
access the mailbox registers. However, an interrupt is needed to be
sent to request the M3 to perform a desired PM operation. This patch
adds the support for
The mailbox DT node data has been added for AM33xx device, with
information added currently for communicating with WkupM3
processor. The usr_id value in the DT node reflects the value
used for MPU like the rest of the SoCs. The driver logic will
be adjusted to account for the WkupM3 usr_id within
Add the mailbox device DT node for OMAP5 SoC.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index e643620..a08f1ca 100644
---
Hi,
I get the following on Amstrad Delta (E3) when booting unpatched
v3.11-rc4. The kernel config is after the crash.
Uncompressing Linux... done, booting the kernel.
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version
Hi Mark,
On Tue, Aug 6, 2013 at 12:49 PM, Mark Brown broo...@kernel.org wrote:
From: Andy Green andy.gr...@linaro.org
You might have CONFIG_PM, but you might not have CONFIG_SUSPEND, in which
case these are unused.
Signed-off-by: Andy Green andy.gr...@linaro.org
Signed-off-by: Mark Brown
On Tue, Aug 06, 2013 at 03:37:13PM +0200, Alexander Holler wrote:
Am 06.08.2013 12:14, schrieb Greg Kroah-Hartman:
What exactly is a platform device anyway?
Originally it was a something that wasn't connected to a bus, but just
had memory-mapped i/o. Like the PS2 keyboard controller.
On Tue, Aug 06, 2013 at 01:27:35PM +0300, Pantelis Antoniou wrote:
Hi Greg,
On Aug 6, 2013, at 1:15 PM, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote:
Hi Greg,
On Aug 6, 2013, at 12:36 PM, Greg Kroah-Hartman wrote:
On Tue, Aug 06,
On Tue, Aug 06, 2013 at 11:19:14AM +0100, Russell King - ARM Linux wrote:
On Tue, Aug 06, 2013 at 06:15:27PM +0800, Greg Kroah-Hartman wrote:
On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote:
What would it take to move all this into driver core?
What specifically would
67 matches
Mail list logo
