Gentle Ping
On Monday 02 March 2015 04:19 PM, Vignesh R wrote:
This patches makes following changes to omap_hdq driver
- Enable 1-wire mode.
- Implement w1_triplet callback to facilitate search rom
procedure and auto detection of 1-wire slaves.
- Proper enabling and disabling of
On 17/03/15 20:02, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [150317 07:55]:
Hi,
On Tue, Mar 17, 2015 at 11:43:51AM +0200, Roger Quadros wrote:
Now that we have EXTCON_USB_GPIO queued for v4.1, revert
commit addfcde7c485 (ARM: dts: dra7x-evm: beagle-x15: Fix USB Host)
On these EVMs,
Two trivialities I failed the spot the first time.
On Tue, 2015-03-17 at 17:12 -0700, Tony Lindgren wrote:
diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
index 2962de2..c858c2b 100644
--- a/drivers/phy/Kconfig
+++ b/drivers/phy/Kconfig
+config PHY_DM816X_USB
+ tristate TI
On 03/17/2015 04:56 PM, Jyri Sarha wrote:
Set a rule constraints to allow only combinations of sample-rate and
number of frame-bits that can be played/captured with a reasonable
sample-rate accuracy.
Also, takes the number of serializers into account when implicitly
selecting the BLCK
Hi Tony,
I think it's good to remove this legacy code.
Will let u know once I got the booting dst.
Best regards,
Jason Lam
Embedded Machine Technology Co., Ltd
Tel: +86-020-87643879-830
Fax: +86-020-87245492
Mobile: +86-13828455425
Email: l...@ema-tech.com
Website: http://www.ema-tech.com
Use new binding for the external tda19988 HDMI encoder.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
arch/arm/boot/dts/am335x-boneblack.dts | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-boneblack.dts
Force crtc dpms off before destroying the crtc instead of just
checking the dpms state. This fixes warning message and frozen picture
after tilcdc module unloading.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 3 ++-
1 file changed, 2 insertions(+), 1
Adds a CONFIG_DRM_TILCDC_SLAVE_COMPAT module for ti,tilcdc,slave
node conversion. The implementation is in tilcdc_slave_compat.c and it
uses tilcdc_slave_compat.dts as a basis for creating a DTS
overlay. The DTS overlay adds an external tda998x encoder to tilcdc
that corresponds to the old tda998x
Remove tilcdc slave support for tda998x driver. The tilcdc slave
support would conflicts with componentized use of tda998x.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
.../devicetree/bindings/drm/tilcdc/slave.txt | 18 -
drivers/gpu/drm/tilcdc/Makefile| 1 -
This patch should be dropped/reverterd if/after of: Decrement refcount
of previous endpoint in of_graph_get_next_endpoint patch has been
merged.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/gpu/drm/tilcdc/tilcdc_external.c | 1 +
1 file changed, 1 insertion(+)
diff --git
If I read Documentation/kbuild/makefiles.txt section 3.6 right, this
patch should not be needed. However, without this patch the objects
needed for DRM_TILCDC_SLAVE_COMPAT are not linked, if DRM_TILCDC is
built as module.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/gpu/drm/Makefile | 2
Add support for an external compontised DRM encoder. The external
encoder can be connected to tilcdc trough device tree graph binding.
The binding document for tilcdc has been updated. The current
implementation supports only tda998x encoder.
I got the idea and some lines of code from
I think the patches 1-5 are ready for merging. See the details below.
I moved the drm/tilcdc: Decrement refcount of ep-node from
of_graph_get_next_endpoint to last in the set and I think it can be
dropped. The of: Decrement refcount of previous endpoint in
of_graph_get_next_endpoint is eventually
And we also need to populate the tables along the lines of 27b7d5f3cc49
(bus: omap_l3_noc: Add AM4372 interconnect error data).
I think intercon data should be in DT rather than some hardcoded table.
Do the below ranges match your JTAG results?
Yup. Based a memory dump I had done earlier,
Hi,
On Wednesday 18 March 2015 05:51 PM, Linus Walleij wrote:
On Mon, Mar 16, 2015 at 9:46 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
On Wednesday 14 January 2015 05:28 PM, Linus Walleij wrote:
#include linux/reboot.h
static int foo_reboot_handler(struct notifier_block *this,
On Mon, Mar 16, 2015 at 9:46 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
On Wednesday 14 January 2015 05:28 PM, Linus Walleij wrote:
#include linux/reboot.h
static int foo_reboot_handler(struct notifier_block *this,
unsigned long code,
There is no need to call this separately from io.c, rather this can be
done commonly under the PRM driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |4
arch/arm/mach-omap2/prm44xx.c |2 ++
2 files changed, 2 insertions(+), 4 deletions(-)
diff
Hi,
Changes in this set compared to v3:
- Changed the SCM module DT node layout based on comments from Tony;
basically the wkup / core are split into their own nodes now. This
applies for omap3, omap4, omap5 and dra7, rest of the SoCs have their
control module integrated as one instance
* Paul Bolle pebo...@tiscali.nl [150318 04:13]:
Two trivialities I failed the spot the first time.
On Tue, 2015-03-17 at 17:12 -0700, Tony Lindgren wrote:
diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
index 2962de2..c858c2b 100644
--- a/drivers/phy/Kconfig
+++
Hi,
[NOTE: RFC only. Not for merge yet.]
This is an attempt to centralize OTG functionality in the kernel.
Still work in progress but I wanted to get an early feedback
to avoid major rework. :)
Why?:
Most of the OTG drivers have been dealing with the OTG state machine
themselves and
The OTG state machine needs a mechanism to start and
stop the gadget controller. Add usb_gadget_start()
and usb_gadget_stop().
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/gadget/udc/udc-core.c | 166 +++---
include/linux/usb/gadget.h| 3 +
To support OTG we want a mechanism to start and stop
the HCD from the OTG state machine. Add usb_start_hcd()
and usb_stop_hcd().
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/core/hcd.c | 147
include/linux/usb/hcd.h | 2 +
2 files
This is the a_set_b_hnp_enable flag in the OTG state machine
diagram and must be set when the A-Host has successfully set
the b_hnp_enable feature of the OTG-B-Peripheral attached to it.
When this bit changes we kick our OTG FSM to make note of the
change and act accordingly.
Signed-off-by:
PRM driver now only exports a generic API for clearing / checking
VP txdone status.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prm.h | 14 ++
arch/arm/mach-omap2/prm3xxx.c |6 --
arch/arm/mach-omap2/prm3xxx.h |4
There is no need to call this separately from io.c, rather this can be
done commonly under the CM driver. Also, this patch makes the API static,
as it is no longer used outside the driver file.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/cm44xx.h |1 -
OMAP4 has different ordering of PRM and CM init calls in the early init.
Re-oder these accordingly for OMAP4 also. This is needed so that we
can do some optimizations in the following patches for the PRCM init.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |2 +-
1
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case where both the provider index
and register offsets are zero. In this case, the current error checking
against a NULL pointer will fail. Thus, change the API to return a
ERR_PTR value in an error
OMAP2/3 now use generic API for the prm_clear_mod_irqs, the SoC specific
implementation details are provided through prm_ll_data.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm24xx.c | 24 +++-
arch/arm/mach-omap2/pm34xx.c | 18
This avoids conflicts in the global namespace, and is more descriptive
of the purpose anyway.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |2 +-
arch/arm/mach-omap2/prm.h|2 +-
arch/arm/mach-omap2/prm_common.c |8 +++-
3 files changed,
This makes the API the same as used with OMAP2, and makes it possible
to implement a generic driver API for the functionality.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm34xx.c | 18 +-
arch/arm/mach-omap2/prm3xxx.c |8
struct otg_fsm is the interface to the OTG state machine.
Document the input, output and internal state variables.
Definations are taken from Table 7-2 and Table 7-4 of
the USB OTG EH Specification Rev.2.0
Re-arrange some of the members as per use case for more
clarity.
Signed-off-by: Roger
Register with OTG core as part of usb_add_hcd() and
unregister from it in usb_remove_hcd().
For OTG device the HCD is actually started or stopped
from the OTG FSM.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/core/hcd.c | 14 ++
1 file changed, 10 insertions(+), 4
The OTG core instantiates the OTG Finite State Machine
per OTG controller and manages starting/stopping the
host and gadget controllers based on the bus state.
It provides APIs for the following tasks
- Registering an OTG capable controller
- Registering Host and Gadget controllers to OTG core
-
Register with the USB OTG core.
Use extcon framework to get VBUS/ID cable events and
kick the OTG state machine.
TODO:
- OTG driver ops to configure dwc3 otg core during role switches.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/dwc3/core.c | 101
Register with OTG core as part of usb_add_gadget_udc_release()
and unregister from it in usb_del_gadget_udc().
In the OTG use case we may not yet be in b_peripheral
state so we shouldn't allow starting the UDC till
OTG core says so.
Signed-off-by: Roger Quadros rog...@ti.com
---
These members are not used anywhere so remove them.
Signed-off-by: Roger Quadros rog...@ti.com
---
include/linux/usb/otg-fsm.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/include/linux/usb/otg-fsm.h b/include/linux/usb/otg-fsm.h
index b6ba1bf..176c4fc 100644
---
On Tue, Mar 17, 2015 at 06:18:37PM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [150317 17:32]:
Hi,
On Tue, Mar 17, 2015 at 05:19:20PM -0700, Tony Lindgren wrote:
Looks like we have cppi41 on dm816x just like on am335x.
Cc: Bin Liu binml...@gmail.com
Cc: Brian
Hi All,
On 02/25/2015 08:08 PM, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko grygorii.stras...@linaro.org
Setting a dev_pm_ops resume callback but not a set of
hibernation handler means that pm function will not be
called upon hibernation.
Fix this by using SIMPLE_DEV_PM_OPS,
Quoting Fabian Frederick (2015-03-16 12:59:06)
of_device_id is always used as const.
(See driver.of_match_table and open firmware functions)
Signed-off-by: Fabian Frederick f...@skynet.be
Acked-by: Michael Turquette mturque...@linaro.org
---
drivers/clk/clk-palmas.c | 2
This shall not be used anymore, as control module driver is converted
into using regmap.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/control.c |5 -
arch/arm/mach-omap2/control.h |2 --
2 files changed, 7 deletions(-)
diff --git a/arch/arm/mach-omap2/control.c
Pinmux node should be a reference to the base one, not a complete re-write
of it. Having the node like this also prevents modifying the node layout
in the base am4372.dtsi file, which is needed for control module changes.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
Control module driver needs to support syscon for register accesses, as
the DT hierarchy for control module driver is going to be changed. All
the control module related features will be moved under control module
node, including clocks, pinctrl, and generic configuration register
access.
omap4_ctrl_pad_readl/writel are no longer used by anybody, so remove
these. Syscon / pinctrl should be used to access the padconf area
instead.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/control.c | 24 +---
arch/arm/mach-omap2/control.h |5 +
Currently some cpu_is_X checks are used to setup prm_features, however
the same can be accomplished by just passing these flags from the PRM
init data. This is done in preparation to make PRM a separate driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prm44xx.c|
PRM device instance offset is now provided through the prm_init_data.
This gets rid of some cpu_is_X / soc_is_X calls from PRM core code,
preparing for PRM to be its own separate driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prcm-common.h |2 ++
The compatible DT node is now passed with the prm init, so there is no
need to do node matching here again. Added a new flag to the init data
also, to detect default IRQ support for OMAP4. Also, any booting omap4
DT setup always has a PRM node, so there is no need to check against
the special case
Add node for system control module, and move all the existing system
control IO space users under this new node as its children. A new node
for scm_conf area is also added.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
.../devicetree/bindings/arm/omap/ctrl.txt |2 +
This patch moves all the control module related features under scrm node.
scm_conf area is changed to use syscon, and also the clocks are moved
under scm_conf area.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi| 33 +-
There is no need to read the register with every invocation of the function,
as the value is constant. Thus, cache the value in a static variable.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/id.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
Add node for system control module, and move all the existing system
control IO space users under this new node as its children. A new node
for scm_conf area is also added.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
.../devicetree/bindings/arm/omap/ctrl.txt |2 +
There is no need to provide the control module base address through a
low-level API from the low-level IO init, as this information is
available through DT. This patch adds a new API to initialize the
control module though, but mostly makes the old API obsolete. The
old API can be completely
This gets rid of need for some exported driver APIs, and simplifies the
initialization of the PRM driver. Done in preparation to make PRM a
separate driver. The init data is now also passed to the SoC specific
implementations, allowing future expansion to add feature flags etc.
Signed-off-by:
Splits the clock related provider module inits under their own driver files.
Previously this was done for all modules under the common PRM driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/cm.h |1 +
arch/arm/mach-omap2/cm_common.c | 51
OMAP4, OMAP5 and DRA7 now parse DT entries for control module address spaces,
and set up syscon mappings appropriately. Low level IO init is updated to
remove the legacy control module mappings for these devices also.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/control.c |
This patch moves all the control module related features under scrm
node. scm_conf area is changed to use syscon, and also the clocks
are moved under scm_conf area.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 48 -
1
Splits the clock provider init out of the PRM driver and moves it to
clock driver. This is needed so that once the PRCM drivers are separated,
they can logically just access the clock driver not needing to go through
common PRM code. This would be wrong in the case of control module for
example.
The legacy control module APIs will be gone, thus convert the display
driver to use syscon. This change should eventually be moved to
display driver from the board directory.
Signed-off-by: Tero Kristo t-kri...@ti.com
Cc: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/display.c |
There is no need to provide the CM base address through a low-level API
from the low-level IO init, as this information is available through DT.
Re-routed the parsing function to be called from the CM drivers also to
simplify the implementation under io.c.
Signed-off-by: Tero Kristo
There is no need to provide the PRM base address through a low-level API
from the low-level IO init, as this information is available through DT.
Re-routed the parsing function to be called from the PRM drivers also to
simplify the implementation under io.c.
Signed-off-by: Tero Kristo
This patch moves all the control module related features under scrm node.
scm_conf area is changed to use syscon, and also the clocks are moved
under scm_conf area.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
.../devicetree/bindings/arm/omap/prcm.txt |1 +
This gets rid of need for some exported driver APIs, and simplifies the
initialization of the CM driver. Done in preparation to make CM a
separate driver. The init data is now also passed to the SoC specific
implementations, allowing future expansion to add feature flags etc.
Signed-off-by: Tero
This patch moves all the control module related features under scrm
node. scm_conf area is provided to support syscon, and also the clocks
are moved under scm_conf area.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/boot/dts/am4372.dtsi | 48 +++--
These PRCM nodes were earlier added in patch 7800064ba5 (ARM: dts: Add
basic dm816x device tree configuration), but the documentation for
the same wasn't added. Fix this by adding the missing compatible strings
under the generic prcm.txt document.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
Some of the TI clock providers will be converted to use syscon, thus
low-level regmap support is needed for the clock drivers also. This
patch adds this support, which can be enabled for individual drivers
in later patches.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
Add node for system control module, and move all the existing system
control IO space users under this new node as its children. A new node
for scm_conf area is also added. DT documentation is also updated by
this patch to reflect the existence of system control module nodes,
separately of PRCM
All clock provider related drivers will now register their iomaps
with a static index. This makes it easier to split up the individual
drivers to their own files in subsequent patches.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prcm-common.h |8
Hi Tony,
On Wednesday 18 March 2015 05:42 AM, Tony Lindgren wrote:
Add a minimal driver for dm816x USB. This makes USB work on dm816x
without any other changes needed as it can use the existing musb_dsps
glue layer for the USB controller.
Note that this phy is different from dm814x and am335x.
2015-03-11 5:30 GMT+08:00 Felipe Balbi ba...@ti.com:
On Sun, Feb 22, 2015 at 12:25:35PM +0800, Sneeker Yeh wrote:
These patches add support for XHCI compliant Host controller found
on Fujitsu Socs, and are based on http://lwn.net/Articles/629162/
The first patch is to add Fujitsu glue layer of
On Wed, Feb 25, 2015 at 1:08 PM, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko grygorii.stras...@linaro.org
Setting a dev_pm_ops resume callback but not a set of
hibernation handler means that pm function will not be
called upon hibernation.
Fix this by using
* Felipe Balbi ba...@ti.com [150318 07:41]:
On Tue, Mar 17, 2015 at 06:18:37PM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [150317 17:32]:
Hi,
On Tue, Mar 17, 2015 at 05:19:20PM -0700, Tony Lindgren wrote:
Looks like we have cppi41 on dm816x just like on am335x.
On Wed, Mar 18, 2015 at 5:48 AM, pang.xun...@zte.com.cn wrote:
Ping ...
Thanks for the reminder. Since there's not been any objections, I'm
queuing this up.
thanks
-john
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
From: Luciano Coelho l...@coelho.fi
Instead of defining an enumeration with the FW specific values for the
different clock rates, use the actual frequency instead. Also add a
boolean to specify whether the clock is XTAL or not.
Change all board files to reflect this.
Signed-off-by: Luciano
Now that we have wlcore device-tree bindings in place
(for both wl12xx and wl18xx), remove the legacy
wl12xx_platform_data struct, and move its members
into the platform device data (that is passed to wlcore)
Davinci 850 is the only platform that still set
the platform data in the legacy way (and
Add device-tree support to the wlcore (wl12xx/wl18xx)
driver.
Update the current users to use the bindings instead
of pdata-quirks.
Finally, remove the deprecated wl12xx_platform_data
struct (along with the da850 board file code that
still uses it)
v7:
* rebase (v4.0-rc4)
* fix wlcore_spi
Add device tree binding documentation for TI's wilink
(wl12xx and wl18xx) wlan chip.
Signed-off-by: Eliad Peller el...@wizery.com
---
.../devicetree/bindings/net/wireless/ti,wlcore.txt | 47 ++
1 file changed, 47 insertions(+)
create mode 100644
From: Luciano Coelho l...@coelho.fi
The platform_quirk element in the platform data was used
to change the way the IRQ is triggered. When set,
the EDGE_IRQ quirk would change the irqflags used
and treat edge trigger differently from the rest.
Instead of hiding this irq flag setting behind the
Replace all the pdata-quirks for setting wl12xx/wl18xx
platform data with proper DT definitions.
Signed-off-by: Eliad Peller el...@wizery.com
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Acked-by: Enric Balletbo i Serra eballe...@gmail.com
Tested-by: Tony Lindgren t...@atomide.com
---
When running with device-tree, we no longer have a board file
that can set up the platform data for wlcore.
Allow this data to be passed from DT.
Signed-off-by: Ido Yariv i...@wizery.com
Signed-off-by: Eliad Peller el...@wizery.com
Tested-by: Sébastien Szymanski sebastien.szyman...@armadeus.com
* Kishon Vijay Abraham I kis...@ti.com [150318 08:09]:
On Wednesday 18 March 2015 05:42 AM, Tony Lindgren wrote:
+
+/*
+ * We have phy-core.c handle pm_runtime calls for us. We implement
+ * these functions for phy-core.c to keep track of power_count.
+ * Note that we may want to remove
* Matthijs van Duin matthijsvand...@gmail.com [150318 01:33]:
And we also need to populate the tables along the lines of 27b7d5f3cc49
(bus: omap_l3_noc: Add AM4372 interconnect error data).
I think intercon data should be in DT rather than some hardcoded table.
Yeah so it seems.
Do the
Hi Tony,
As I can see Patch 1 from this series was merged in 4.0-rc4,
but this patch wasn't. As result, I can see below warning all the time during
boot now:
[0.594591] platform 4a094000.pciephy: Cannot lookup hwmod 'pcie1-phy'
On 02/20/2015 10:51 AM, Kishon Vijay Abraham I wrote:
Now
* Grygorii Strashko grygorii.stras...@ti.com [150318 09:37]:
Hi Tony,
As I can see Patch 1 from this series was merged in 4.0-rc4,
but this patch wasn't. As result, I can see below warning all the time during
boot now:
[0.594591] platform 4a094000.pciephy: Cannot lookup hwmod
* Tero Kristo t-kri...@ti.com [150318 00:06]:
On 03/17/2015 08:38 PM, Tony Lindgren wrote:
* Mike Turquette mturque...@linaro.org [150306 11:18]:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case
* Jason l...@ema-tech.com [150318 00:59]:
Hi Tony,
I think it's good to remove this legacy code.
Will let u know once I got the booting dst.
OK I'm planning to queue it for v4.1 merge window then unless
we hear from people using it.
Regards,
Tony
--
To unsubscribe from this list: send the
Hello.
On 03/18/2015 05:44 PM, Tero Kristo wrote:
There is no need to read the register with every invocation of the function,
as the value is constant. Thus, cache the value in a static variable.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/id.c |5 -
1
* grygorii.stras...@linaro.org grygorii.stras...@linaro.org [150318 12:36]:
On 03/18/2015 06:57 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [150318 09:37]:
As I can see Patch 1 from this series was merged in 4.0-rc4,
but this patch wasn't. As result, I can see
Hi Greg,
* Greg Knight g.kni...@symetrica.com [150318 12:38]:
Hi, linux-omap,
I've attached a patch which adds a device-tree field ti,dma-min-bytes
which replaces the macro DMA_MIN_BYTES. Adjusting this field addresses
issues we've had where, in our particular use case, the usleep() in the
On 03/18/2015 06:57 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [150318 09:37]:
As I can see Patch 1 from this series was merged in 4.0-rc4,
but this patch wasn't. As result, I can see below warning all the time
during boot now:
[0.594591] platform
Hi, linux-omap,
I've attached a patch which adds a device-tree field ti,dma-min-bytes
which replaces the macro DMA_MIN_BYTES. Adjusting this field addresses
issues we've had where, in our particular use case, the usleep() in the
SPI worker thread eats a full 20% of our CPU (AM3359).
I opted to
Hi, linux-omap,
I've attached a couple patches to provide support for the Freescale
SGTL5000 chip when using the McASP on the AM3359.
This adds an optional hack, clock-to-talk to the McASP subsystem which
can start AHCLKX/AHCLKR prior to initializing the codec. This is needed
on the SGTL5000,
On 03/17/2015 08:38 PM, Tony Lindgren wrote:
* Mike Turquette mturque...@linaro.org [150306 11:18]:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case where both the provider index
and register offsets
Looks like dm81xx can only do 32-bit fifo reads like am35x. Let's set
up musb-dsps with a custom read_fifo function based on the compatible
flag.
Otherwise we can get the following errors when starting dhclient on a
asix USB Ethernet adapter:
asix 2-1:1.0 eth2: asix_rx_fixup() Bad Header Length
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
Acked-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
.../devicetree/bindings/media/ti,omap3isp.txt | 71
MAINTAINERS|1 +
include/dt-bindings/media/omap3-isp.h
The resources the ISP needs are slightly different on 3[45]xx and 3[67]xx.
Especially the phy-type property is different.
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
Acked-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
arch/arm/boot/dts/omap34xx.dtsi | 17 +
Add support for the primary camera of the Nokia N950 and N9.
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
Acked-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
arch/arm/boot/dts/omap3-n9.dts | 37 +
arch/arm/boot/dts/omap3-n950.dts | 37
Hi folks,
Since v1, I've rebased the set on Tero Kristo's PRCM / SCM cleanup patchset
here:
URL:http://www.spinics.net/lists/linux-omap/msg116949.html
v1 can be found here:
URL:http://www.spinics.net/lists/linux-omap/msg116753.html
Changes since v1:
- Fixed phy reference (number to name) in
Hi Tero,
On Wed, Mar 18, 2015 at 04:43:45PM +0200, Tero Kristo wrote:
Hi,
Changes in this set compared to v3:
- Changed the SCM module DT node layout based on comments from Tony;
basically the wkup / core are split into their own nodes now. This
applies for omap3, omap4, omap5 and
On Wed, 18 Mar 2015, Tony Lindgren wrote:
If the host controller is started more than once, you will end up
unregistering and re-registering the root hub. The device core does
not allow this. Once a device has been unregistered, you must not try
to register it again -- you have to
On Wed, Mar 18, 2015 at 03:55:55PM +0200, Roger Quadros wrote:
To support OTG we want a mechanism to start and stop
the HCD from the OTG state machine. Add usb_start_hcd()
and usb_stop_hcd().
Hi Roger,
You may not need to create another pair of hcd APIs for doing
it, you can use
* Alan Stern st...@rowland.harvard.edu [150318 18:51]:
On Wed, 18 Mar 2015, Tony Lindgren wrote:
If the host controller is started more than once, you will end up
unregistering and re-registering the root hub. The device core does
not allow this. Once a device has been unregistered,
1 - 100 of 116 matches
Mail list logo
