Hi Stephen,
Thanks for your review.
On 8/20/2013 1:01 AM, Stephen Warren wrote:
On 08/16/2013 04:13 AM, George Cherian wrote:
Adding extcon driver for USB ID detection to dynamically
configure USB Host/Peripheral mode.
diff --git a/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
On 20/08/13 02:01, Samuel Ortiz wrote:
Hi Grygorii,
On Thu, Jul 25, 2013 at 04:15:46PM +0300, Grygorii Strashko wrote:
This patch series intorduces twl6030-irq module rework to use Threaded IRQ and
linear irq_domain, and adds support for PMIC TWL6032 IRQs.
After this patch series TWL6030/6032
Now that we have DT bindings to specify which devices on the SoC should not
be reset or idled, get rid of the same information existing as part of the
hwmod data files and pass this info from DT instead.
For GPMC, the HWMOD_INIT_NO_RESET flag seems to be added in hwmod not due to
any errata
On OMAP we have co-processor IPs, memory controllers,
GPIOs which control regulators and power switches to
PMIC, and SoC internal Bus IPs, some or most of which
should either not be reset or idled or both. Have a
way to pass this information from DT.
(In some cases there are erratas which prevent
For modules/IPs/hwmods which do not have
-1- sys-class-reset()
and
-2- hardreset lines
and
-3- No way to do an ocp reset (no sysc control)
the flag 'HWMOD_INIT_NO_RESET' is not much useful.
Cleanup all such instances across various hwmod data files.
Signed-off-by: Rajendra Nayak rna...@ti.com
We have devices like co-processors, SoC internal busses, memory controllers
etc which should not be idled or reset. In some cases erratas around IP blocks
prevent them from either being idled or reset. Have a way to pass this
information from Device tree, and get rid of similar information that
This patch adds alwon powerdomain support for TI81XX, which is required
for stable functioning of a big number of TI81XX subsystems.
Signed-off-by: Aida Mynzhasova aida.mynzhas...@skitlab.ru
---
arch/arm/mach-omap2/powerdomains3xxx_data.c | 8
arch/arm/mach-omap2/prcm-common.h
On Tue, Aug 20, 2013 at 08:13:54AM +0100, Graeme Gregory wrote:
On 20/08/13 02:01, Samuel Ortiz wrote:
Hi Grygorii,
On Thu, Jul 25, 2013 at 04:15:46PM +0300, Grygorii Strashko wrote:
This patch series intorduces twl6030-irq module rework to use Threaded IRQ
and
linear irq_domain, and adds
+ Rajendra and Tero,
Hi Afzal,
On 19/08/2013 08:36, Afzal Mohammed wrote:
Hi Tony,
On Tuesday 13 August 2013 01:31 PM, Tony Lindgren wrote:
Hi Paul Benoit,
Does this series look OK to you guys to queue or ack?
Can you please consider queuing this series for the coming merge window
as
Hi Sebastian,
On Monday 19 August 2013 06:07 PM, Sebastian Andrzej Siewior wrote:
On 08/19/2013 02:27 PM, Jean Pihet wrote:
Hi!
Hi Jean,
You need to add 'earlyprintk' in the kernel command line, given (I
suppose) by U-Boot.
Ah, good hint.
I hope this helps!
Yes. I do not see
Hi Chanwoo,
Thanks for your review.
On 8/20/2013 5:54 AM, Chanwoo Choi wrote:
Hi George,
On 08/16/2013 07:13 PM, George Cherian wrote:
Adding extcon driver for USB ID detection to dynamically
configure USB Host/Peripheral mode.
Signed-off-by: George Cherian george.cher...@ti.com
---
From: Ivan T. Ivanov iiva...@mm-sol.com
DWC3 glue layer is hardware layer around Synopsys DesignWare
USB3 core. Its purpose is to supply Synopsys IP with required
clocks, voltages and interface it with the rest of the SoC.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
From: Ivan T. Ivanov iiva...@mm-sol.com
MSM USB3.0 core wrapper consist of USB3.0 IP from Synopsys
(SNPS) and HS, SS PHY's control and configuration registers.
It could operate in device mode (SS, HS, FS) and host
mode (SS, HS, FS, LS).
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
From: Ivan T. Ivanov iiva...@mm-sol.com
Hi,
Here is fourth version of MSM USB3 drivers patches.
Changes since v3:
* Remove _clk suffix from clock names
* Clarify required child node for qcom,dwc3
* Fix comments in functions headers
* Use dbg instead err in drivers probe functions.
Changes
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
which manage Synopsys DesignWare USB3 controller stack
inside Qualcomm SoC's.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
Hi George,
diff --git a/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
b/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
new file mode 100644
index 000..37e4c22
--- /dev/null
+++ b/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
@@ -0,0 +1,19 @@
On Mon, Aug 19, 2013 at 10:51:51AM +0200, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
Remove unneeded error handling on the result of a call to
platform_get_resource_byname when the value is passed to
devm_ioremap_resource.
Applied, thanks.
signature.asc
Description:
VPE(Video Processing Engine) is an IP found on DRA7xx, this series adds VPE as a
mem to mem v4l2 driver, and VPDMA as a helper library.
The previous revision of the series described VPE in detail, you can have a look
at it here:
http://www.spinics.net/lists/linux-media/msg66518.html
There were
The primary function of VPDMA is to move data between external memory and
internal processing modules(in our case, VPE) that source or sink data. VPDMA is
capable of buffering this data and then delivering the data as demanded to the
modules as programmed. The modules that source or sink data are
Add a DT node for VPE in dra7.dtsi. This is experimental because we might need
to split the VPE address space a bit more, and also because the IRQ line
described is accessible the IRQ crossbar driver is added for DRA7XX.
Cc: Rajendra Nayak rna...@ti.com
Cc: Sricharan R r.sricha...@ti.com
Create functions which the VPE driver can use to create a VPDMA descriptor and
add it to a VPDMA descriptor list. These functions take a pointer to an existing
list, and append the configuration/data/control descriptor header to the list.
In the case of configuration descriptors, the creation of
Add support for the de-interlacer block in VPE.
For de-interlacer to work, we need to enable 2 more sets of VPE input ports
which fetch data from the 'last' and 'last to last' fields of the interlaced
video. Apart from that, we need to enable the Motion vector output and input
ports, and also
Add hwmod data for the VPE IP, this is needed for the IP to be reset during
boot, and control the functional clock when the driver needs it via
pm_runtime apis. Add the corresponding ocp_if struct and add it DRA7XX's
ocp interface list.
Cc: Rajendra Nayak rna...@ti.com
Cc: Sricharan R
Hi Sebastian,
On Tuesday 20 August 2013 03:02 PM, Lokesh Vutla wrote:
Yes. I do not see the decompress messages but I have an early console
later on. Unfortunately it stops now right at the serial core:
|pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
|Serial: 8250/16550
Hi Archit,
On Wednesday 14 August 2013 16:27:57 Archit Taneja wrote:
On Friday 09 August 2013 03:34 AM, Laurent Pinchart wrote:
On Friday 02 August 2013 19:33:38 Archit Taneja wrote:
The primary function of VPDMA is to move data between external memory and
internal processing modules(in
Hi,
On Mon, Aug 19, 2013 at 10:58:09AM +0530, Kishon Vijay Abraham I wrote:
So maybe let's stop solving an already solved problem and just state that
you need to explicitly assign device ID to use this framework?
Felipe,
Can we have it the way I had in my v10 patch series till we find
Hi,
On Tue, Aug 20, 2013 at 12:56:04PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
which manage Synopsys DesignWare USB3 controller stack
inside
* Olof Johansson o...@lixom.net [130816 15:05]:
Our current fixes branch is based on -rc4, and I didn't see any of
these commits in linux-next, so I took the liberty to rebase them back
onto our current branch.
I.e. pulled, but rebased.
Thanks no problem at my end. But to avoid future
On Tuesday 20 August 2013 05:09 PM, Laurent Pinchart wrote:
Hi Archit,
On Wednesday 14 August 2013 16:27:57 Archit Taneja wrote:
On Friday 09 August 2013 03:34 AM, Laurent Pinchart wrote:
On Friday 02 August 2013 19:33:38 Archit Taneja wrote:
The primary function of VPDMA is to move data
Hi Joel,
On Sunday 18 August 2013 08:12 AM, Joel Fernandes wrote:
In early version of this driver, assumptions were made such as DMA layer
requires contiguous buffers etc. Due to this, new buffers were allocated,
mapped and used for DMA. These assumptions are no longer true and DMAEngine
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
Hi,
On Tue, Aug 20, 2013 at 06:35:25PM +0530, Sourav Poddar wrote:
+static int qspi_transfer_msg(struct ti_qspi *qspi, struct spi_transfer *t)
+{
+ int ret;
+
+ if (t-tx_buf) {
+ ret = qspi_write_msg(qspi, t);
+ if (ret) {
+
Hi Laurent,
On Tuesday 20 August 2013 05:09 PM, Laurent Pinchart wrote:
snip
+static int vpdma_load_firmware(struct vpdma_data *vpdma)
+{
+ int r;
+ struct device *dev = vpdma-pdev-dev;
+
+ r = request_firmware_nowait(THIS_MODULE, 1,
+ (const char *)
On Tuesday 20 August 2013 06:44 PM, Felipe Balbi wrote:
Hi,
On Tue, Aug 20, 2013 at 06:35:25PM +0530, Sourav Poddar wrote:
+static int qspi_transfer_msg(struct ti_qspi *qspi, struct spi_transfer *t)
+{
+ int ret;
+
+ if (t-tx_buf) {
+ ret = qspi_write_msg(qspi, t);
+
Hi Artem, Brian,
Changes v4 - v5
- Rebased to linux-next
IMPORTANT: Need to revert commit fb1585b, [PATCH 2/4] part of previous
version
http://lists.infradead.org/pipermail/linux-mtd/2013-July/047441.html
- Swapped PATCH-1 PATCH-2 to maintain bisectibility compilation
On 8/20/2013 3:59 PM, Chanwoo Choi wrote:
Hi George,
diff --git a/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
b/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
new file mode 100644
index 000..37e4c22
--- /dev/null
+++
Hi,
On Tue, 2013-08-20 at 07:29 -0500, Felipe Balbi wrote:
Hi,
On Tue, Aug 20, 2013 at 12:56:04PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
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
Hi,
On Tue, Aug 20, 2013 at 04:32:23PM +0300, Ivan T. Ivanov wrote:
On Tue, Aug 20, 2013 at 12:56:04PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the
Hi Archit,
On Tuesday 20 August 2013 18:46:38 Archit Taneja wrote:
On Tuesday 20 August 2013 05:09 PM, Laurent Pinchart wrote:
snip
+static int vpdma_load_firmware(struct vpdma_data *vpdma)
+{
+int r;
+struct device *dev = vpdma-pdev-dev;
+
+r =
On Tue, 2013-08-20 at 13:20 +, Gupta, Pekon wrote:
Hi Artem, Brian,
I'll try to go through old e-mails now, and especially ubi/ubifs ones,
including yours, and I'll let Brian handle your patches, if I can? :-)
I checked them, and they looked good to me:
Signed-off-by: Artem Bityutskiy
Hi,
On Tue, 2013-08-20 at 08:37 -0500, Felipe Balbi wrote:
Hi,
On Tue, Aug 20, 2013 at 04:32:23PM +0300, Ivan T. Ivanov wrote:
On Tue, Aug 20, 2013 at 12:56:04PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and
On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 08:37 -0500, Felipe Balbi wrote:
Hi,
On Tue, Aug 20, 2013 at 04:32:23PM +0300, Ivan T. Ivanov wrote:
On Tue, Aug 20, 2013 at 12:56:04PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov
Hi,
On Tue, 2013-08-20 at 09:33 -0500, Felipe Balbi wrote:
On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 08:37 -0500, Felipe Balbi wrote:
Hi,
On Tue, Aug 20, 2013 at 04:32:23PM +0300, Ivan T. Ivanov wrote:
On Tue, Aug 20, 2013
omap-control device is present from OMAP4 onwards which
support device tree boots only. So get rid of platform data.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/phy/phy-omap-control.c | 18 +++---
include/linux/usb/omap_control_usb.h |4
2 files changed, 7
Hi,
This patchset does the following:
* Get rid of omap_control_usb platform data as we support DT only.
* Restructure and add support for new PHY types. We now support the follwing
four types
TYPE_OMAP - if it has otghs_control mailbox register (e.g. on OMAP4)
TYPE_USB2 - if it has Power
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 support non-DT boot, we just bail out on probe
if device node
Add support for new device types and in the process rid of ti,type
device tree property. The correct type of device will be determined
from the compatible string instead.
Introduce a compatible string for each device type. At the moment
we support 4 types Mailbox, USB2, USB3 and DRA7.
Update DT
Split otghs_ctrl and USB2 PHY power down into separate
omap-control-usb nodes. Get rid of ti,type property.
Also get rid of ti,has-mailbox property from usb_otg_hs
node and provide the ctrl-module phandle.
CC: Benoit Cousson bcous...@baylibre.com
Signed-off-by: Roger Quadros rog...@ti.com
---
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.
Also get rid of ti,has-mailbox property as it is redundant and
we can
Split USB2 PHY and USB3 PHY into separate omap-control-usb
nodes. Get rid of ti,type property.
CC: Benoit Cousson bcous...@baylibre.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 20
1 files changed, 12 insertions(+), 8 deletions(-)
diff
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
---
drivers/usb/phy/phy-omap-control.c | 31 ++-
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 support non-DT boot, we just bail out on probe
if device node
Hi Tony,
Please pull the following commits for OMAP Device Tree for v3.12.
Thanks,
Benoit
Add the minimal DTS support for DRA7xx based SoC core.
Add the initial support for N900 and gta04 phones.
Do a lot of various cleanups.
On Aug 20, 2013, at 9:54 AM, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 09:33 -0500, Felipe Balbi wrote:
On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 08:37 -0500, Felipe Balbi wrote:
Hi,
On Tue, Aug 20, 2013 at 04:32:23PM +0300,
This patch series updates the following for the driver:
- Enable polling mode if DMA fails.
- Correct the DMA burst size.
Lokesh Vutla (2):
crypto: omap-sham: Enable Polling mode if DMA fails
crypto: omap-sham: correct dma burst size
drivers/crypto/omap-sham.c | 72
Each cycle of SHA512 operates on 32 data words where as
SHA256 operates on 16 data words. This needs to be updated
while configuring DMA channels. Doing the same.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/omap-sham.c | 11 ---
1 file changed, 4 insertions(+), 7
For writing input buffer into DATA_IN register current driver
has the following state machine:
- if input buffer 9 : use fallback driver
- else if input buffer block size : Copy input buffer into data_in regs
- else use dma transfer.
In cases where requesting for DMA channels fails for some
On Tue, 2013-08-20 at 16:01 +0100, Kumar Gala wrote:
On Aug 20, 2013, at 9:54 AM, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 09:33 -0500, Felipe Balbi wrote:
On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 08:37 -0500, Felipe
Hello Roger,
this will not work!
Roger Quadros wrote on 2013-08-20:
- struct omap_control_usb_platform_data *pdata =
- dev_get_platdata(pdev-dev);
+
+ if (np) {
+ of_property_read_u32(np, ti,type, control_usb-type);
here you are dereferencing
On Tue, 2013-08-20 at 10:01 -0500, Kumar Gala wrote:
On Aug 20, 2013, at 9:54 AM, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 09:33 -0500, Felipe Balbi wrote:
On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 08:37 -0500, Felipe
On Sun, Aug 18, 2013 at 10:49 PM, Gururaja Hebbar
gururaja.heb...@ti.com wrote:
On 8/15/2013 4:04 AM, Russ Dill wrote:
On Wed, Aug 14, 2013 at 3:18 AM, Gururaja Hebbar gururaja.heb...@ti.com
wrote:
On 8/14/2013 3:50 AM, Russ Dill wrote:
Changes since v1:
* Rebased onto new am335x PM
On 08/20/2013 11:18 AM, Samuel Ortiz wrote:
On Tue, Aug 20, 2013 at 08:13:54AM +0100, Graeme Gregory wrote:
On 20/08/13 02:01, Samuel Ortiz wrote:
Hi Grygorii,
On Thu, Jul 25, 2013 at 04:15:46PM +0300, Grygorii Strashko wrote:
This patch series intorduces twl6030-irq module rework to use
On 08/19/2013 03:11 PM, Wolfram Sang wrote:
Hi,
Which means your original patch starts to make a lot more sense. I
wonder is this is really what we should be doing though - breaking out
of the loop, I mean.
Yup, that is fine. I applied the old patch with Acks from Hein and
Felipe to -next.
On Fri, Aug 09, 2013 at 11:18:43AM +0200, Javier Martinez Canillas wrote:
On Thu, Aug 8, 2013 at 11:32 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
Fix the option description to match the other TI SoCs.
This is just a cosmetic change.
Signed-off-by: Ezequiel Garcia
On 08/20/2013 12:55 AM, George Cherian wrote:
Hi Stephen,
Thanks for your review.
On 8/20/2013 1:01 AM, Stephen Warren wrote:
On 08/16/2013 04:13 AM, George Cherian wrote:
Adding extcon driver for USB ID detection to dynamically
configure USB Host/Peripheral mode.
diff --git
On Tue, 2013-08-20 at 16:06 +0100, Pawel Moll wrote:
On Tue, 2013-08-20 at 16:01 +0100, Kumar Gala wrote:
On Aug 20, 2013, at 9:54 AM, Ivan T. Ivanov wrote:
Hi,
On Tue, 2013-08-20 at 09:33 -0500, Felipe Balbi wrote:
On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov
Hello.
On 08/20/2013 06:56 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.
Also get rid of
The newly added omap4 support in the driver was added without
consideration for building older configs. When building omap1_defconfig,
it resulted in:
drivers/char/hw_random/omap-rng.c:190:12: warning: 'omap4_rng_init' defined but
not used [-Wunused-function]
On Tue, Aug 20, 2013 at 7:02 AM, Artem Bityutskiy dedeki...@gmail.com wrote:
On Tue, 2013-08-20 at 13:20 +, Gupta, Pekon wrote:
Hi Artem, Brian,
I'll try to go through old e-mails now, and especially ubi/ubifs ones,
including yours, and I'll let Brian handle your patches, if I can? :-)
Hi,
[ added some people from TI ]
On 8/7/2013 6:05 PM, majianpeng wrote:
V2:
clean up code.
V1:
www.mail-archive.com/linux-omap@vger.../msg93239.html
We found a problem when we removed a working sd card that the irqaction
of omap_hsmmc can sleep to 3.6s. This cause our
Here are some basic OMAP test results for Linux v3.11-rc6.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.11-rc6/20130818180958/
Test summary
Build: uImage:
Pass (14/14): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
Hi folks,
catching up on this thread.
On 08/06/2013 12:49 PM, Dave Gerlach wrote:
+
+static int am33xx_pm_suspend(void)
+{
+ int i, j, ret = 0;
+
+ int status = 0;
+ struct platform_device *pdev;
+ struct omap_device *od;
+
+ /*
+ * By default the following
+
+if (dra7xx_usb-irq_gpio) {
+status = devm_request_threaded_irq(dra7xx_usb-dev, irq_num,
+NULL, id_irq_handler, IRQF_SHARED |
+IRQF_ONESHOT | IRQF_TRIGGER_FALLING,
+dev_name(pdev-dev), (void *) dra7xx_usb);
+if (status)
Hi
a few comments
On Wed, 14 Aug 2013, Suman Anna wrote:
The remoteproc infrastructure is currently tied closely with the
virtio/rpmsg framework, and the boot requires that there are virtio
devices present in the resource table from the firmware image.
Using static channels is something
Hi
On Tue, 23 Jul 2013, Rajendra Nayak wrote:
With support to parse clock data from DT, move all main and optional
clock information from hwmod to DT.
We still retain clocks in hwmod for devices which do not have a DT node.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
Hi Benoît,
On Wed, 17 Jul 2013, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
Long overdue patches to add the device tree updates and
documentation for the SHAM and AES modules on the am33xx.
The supporting code is already in the mainline kernel.
This series is based
On 08/20/2013 07:57 AM, Lokesh Vutla wrote:
Hi Joel,
On Sunday 18 August 2013 08:12 AM, Joel Fernandes wrote:
In early version of this driver, assumptions were made such as DMA layer
requires contiguous buffers etc. Due to this, new buffers were allocated,
mapped and used for DMA. These
Hi Sebastian
On Sun, 11 Aug 2013, Sebastian Reichel wrote:
From: Sebastian Reichel s...@ring0.de
This patch adds Synchronous Serial Interface (SSI) hwmod support for
OMAP34xx SoCs.
a few comments:
- please add your Signed-off-by: to the patch description, per
On Sun, Jul 14, 2013 at 02:24:49AM +0530, Pekon Gupta wrote:
ECC scheme on NAND devices can be implemented in multiple ways.Some using
Software algorithm, while others using in-build Hardware engines.
omap2-nand driver currently supports following flavours of ECC schemes.
Hi Pekon,
I don't think I will take this series (at least not yet), because of the
device-tree ABI breakage.
On Sun, Jul 14, 2013 at 02:24:47AM +0530, Pekon Gupta wrote:
Changes v4 - v5
- Rebased to linux-next
IMPORTANT: Need to revert commit fb1585b, [PATCH 2/4] part of previous version
Hi
On Tue, 9 Jul 2013, Rajendra Nayak wrote:
This series adds the data files for DRA7xx devices for
PRCM, hwmod and DT. This is dependent on the core support [1]
patches for DRA7xx and leaves out the clock data since its
on its way to DT [2]
The regbit headers for prm and cm are cleaned
Hi
On Fri, 2 Aug 2013, Afzal Mohammed wrote:
AM43x PRCM support (excluding clock tree) is being added with this
series. AM43x reuses most of the IP's from AM335x, as that is the
case, much of the AM335x hwmod data is reused.
...
Currently there is no public TRM available for AM43x.
Can
On Fri, 2 Aug 2013, Afzal Mohammed wrote:
Add AM43x CMINST, CDOFFS, RM_RSTST RM_RSTCTRL definitions - minimal
ones that would be used.
Signed-off-by: Afzal Mohammed af...@ti.com
...
+/* PRM instances */
+#define AM43XX_PRM_OCP_SOCKET_INST 0x
+#define
Hi Olof,
On Tuesday 20 August 2013 11:37 PM, Olof Johansson wrote:
The newly added omap4 support in the driver was added without
consideration for building older configs. When building omap1_defconfig,
it resulted in:
drivers/char/hw_random/omap-rng.c:190:12: warning: 'omap4_rng_init'
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
---
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 |
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
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. 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
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
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
94 matches
Mail list logo
