Hi,
has commit 3b72c2fe0c6bbec42e (drivers: net:ethernet: cpsw: add
support for VLAN) introduced a bug by defining CPSW_VLAN_AWARE as
BIT(1) instead of BIT(2)?
+#define CPSW_VLAN_AWAREBIT(1)
snip
/* switch to vlan unaware mode */
- cpsw_ale_control_set(priv-ale, 0,
-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/gpmc-nand.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2/gpmc-nand.c
index 17cd393..93914d2 100644
--- a/arch/arm/mach-omap2/gpmc
On Tue, 2014-07-08 at 06:25 +, Gupta, Pekon wrote:
Do you plan to re-spin this patch with above comments, and mark it for stable?
It would be helpful for all OMAP3 users.
Thanks for the reminder. I'll respin the patchset this weekend.
-- Christoph
--
To unsubscribe from this list: send
Most dt omap3 boards configure nand-ecc-opt as bch8. Due
to lack of hardware elm support, bch8 software implementation
gets set.
Since commit 0611c41934ab35ce84dea ARM: OMAP2+: gpmc: update
gpmc_hwecc_bch_capable() for new platforms and ECC schemes,
nand support stops working.
This patch allows
Node usbhshost is supporting pinctrl, so the deprecated
quirk call can be removed.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3-lilly-a83x.dtsi |3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-lilly-a83x.dtsi
b/arch/arm/boot
This patch fixes audio support for omap3-lilly-a83x.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3-lilly-a83x.dtsi |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-lilly-a83x.dtsi
b/arch/arm/boot/dts/omap3-lilly-a83x.dtsi
Init pinctrl-single as postcore, because without this patch omap_gpio is
deferring probe which results in more deferring and finally NFS-Boot
doesn't work.
Diff of bootlog with (good) and without (fail) this patch:
--- good
+++ fail
@@ -60,15 +60,22 @@
cpuidle: using governor ladder
cpuidle:
This set of patches updates board support for omap3-lilly-a83x.
Christoph Fritz (5):
[RFC-HACK] pinctrl-single: init by postcore_initcall()
[RFC-HACK] ARM: dts: OMAP3: reorder pinmux_gpio1_pins
ARM: dts: omap3: set mcbsp2 status
[RFC] ARM: OMAP2+: gpmc: fix gpmc_hwecc_bch_capable
ARM
pinctrl-single for omap3_pmx_core2 gets deferred which results in
some corrupt IRQs so that mmc, spi and dss stop working.
Diff of bootlog with (good) and without (fail) this patch:
--- good
+++ fail
cpuidle: using governor ladder
cpuidle: using governor menu
Reprogramming SDRC clock to
On Thu, 2014-05-22 at 16:28 -0700, Tony Lindgren wrote:
* Christoph Fritz chf.fr...@googlemail.com [140522 16:07]:
This set of patches updates board support for omap3-lilly-a83x.
Christoph Fritz (5):
[RFC-HACK] pinctrl-single: init by postcore_initcall()
I would prefer to start
On Wed, 2014-03-05 at 15:07 +0200, Tero Kristo wrote:
On 03/01/2014 12:37 AM, Tony Lindgren wrote:
* Christoph Fritz chf.fr...@googlemail.com [140214 06:24]:
Full device tree support for clock control, especially to set frequencies,
is not yet accomplished. Until then, configure the 24Mhz
On Fri, 2014-02-28 at 14:38 -0800, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [140214 06:38]:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git work/dss-dt
That way you have it ready and tested if DSS DT goes forward.
Applying only patches 1 2 into
Full device tree support for clock control, especially to set frequencies,
is not yet accomplished. Until then, configure the 24Mhz of sys_clkout2 to
feed an USB-Hub here.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/pdata-quirks.c | 37
Full device tree support for omapdss is not yet accomplished. Until
then, init display by legacy platform code.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/dss-common.c | 49
arch/arm/mach-omap2/dss-common.h |1
INCOstartec LILLY-A83X module is a TI DM3730xx100 (OMAP3) SoC
computer-on-module.
This patch adds device tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 459 +++
1 file
INCOstartec LILLY-DBB056 is a carrier board (baseboard) for
computer-on-module LILLY-A83X.
This patch adds device-tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-lilly
):
- based on next-20140115
Christoph Fritz (4):
ARM: dts: omap3: Add support for INCOstartec a83x module
ARM: dts: omap3: Add support for INCOstartec DBB056 baseboard
ARM: OMAP2+: add legacy display for omap3 DBB056
ARM: OMAP2+: Add pdata quirk for sys_clkout2 for omap3 DBB056
arch/arm
:
Tested-by: Christoph Fritz chf.fr...@googlemail.com
to your series OMAP: OMAP3 DSS related clock patches.
The only issue left on current mainline for a83x board is that twl4030
(tps65920) doesn't set VIO as on next-20140120.
Thanks
-- Christoph
--
To unsubscribe from this list: send
On Fri, 2014-02-07 at 15:49 +0200, Tomi Valkeinen wrote:
On 07/02/14 12:12, Christoph Fritz wrote:
Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want,
you can add my:
Tested-by: Christoph Fritz chf.fr...@googlemail.com
Below is my clock fix for dss:
From
On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
Currently I only analyzed sys_clkout2 (see attachments for full
clk_summary files):
clk_summary__next-20140115__works_as_expected:
dpll4_m2_ck1 1
On Mon, 2014-01-27 at 01:33 +0100, Christoph Fritz wrote:
This set of patches adds board support for an omap3 system from INCOstartec.
It's based on next-20140124.
Due to a regression since next-20140115 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz
On Sat, 2014-02-01 at 19:52 +0100, Christoph Fritz wrote:
On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote:
To help us debug similar problems, I wrote a tool today:
https://github.com/nmenon/ctt-dump - it is a simple memory read utility,
Input file is CTT dump-out
On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote:
To help us debug similar problems, I wrote a tool today:
https://github.com/nmenon/ctt-dump - it is a simple memory read utility,
Input file is CTT dump-out
For example: 3630 CTT is here:
On Wed, Jan 29, 2014 at 04:57:00PM +0200, Tero Kristo wrote:
Hmm, well, the omap96m_alwon_fck rate is still wrong. Try adding
ti,min-div = 2; and ti,max-div = 4; to properties of the clock
node.
Hmm, doesn't change anything here.
Thanks
-- Christoph
--
To unsubscribe from this list: send
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by the fourth patch
in this set
On Tue, 2014-01-28 at 11:04 +0200, Tomi Valkeinen wrote:
On 2014-01-27 20:41, Christoph Fritz wrote:
On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote:
linux-next-20140124 DSS is broken on N900 - display stays black (there
is some noise though). I booted the kernel with qemu
On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote:
linux-next-20140124 DSS is broken on N900 - display stays black (there
is some noise though). I booted the kernel with qemu and it gives the
following warning:
[0.623779] DSS: set fck to 17280
[0.624237] [
Hi Nishanth,
thanks for reviewing this patch. Please see my comments below.
On Wed, Jan 22, 2014 at 01:33:21PM -0600, Nishanth Menon wrote:
On 01/22/2014 01:04 PM, Christoph Fritz wrote:
Full device tree support for clock control is not yet accomplished. Until
then, configure the 24Mhz
Hi Nishanth,
thanks for reviewing this patch. Please see my comments below.
On Wed, Jan 22, 2014 at 01:48:14PM -0600, Nishanth Menon wrote:
On 01/22/2014 01:04 PM, Christoph Fritz wrote:
+ regulators {
+ compatible = simple-bus;
Shrug, just moving the fixed regulator to root
INCOstartec LILLY-A83X module is a TI DM3730xx100 (OMAP3) SoC
computer-on-module.
This patch adds device tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 459 +++
1 file
(v2):
- rebased on next-20140122 from next-20140115
- using omap36xx.dtsi instead of unsupported 1ghz omap37xx100
Initial version (v1):
- based on next-20140115
Christoph Fritz (4):
ARM: dts: omap3: Add support for INCOstartec a83x module
ARM: dts: omap3: Add support for INCOstartec DBB056
INCOstartec LILLY-DBB056 is a carrier board (baseboard) for
computer-on-module LILLY-A83X.
This patch adds device-tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-lilly
Full device tree support for omapdss is not yet accomplished. Until
then, init display by legacy platform code.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/dss-common.c | 49
arch/arm/mach-omap2/dss-common.h |1
Full device tree support for clock control, especially to set frequencies,
is not yet accomplished. Until then, configure the 24Mhz of sys_clkout2 to
feed an USB-Hub here.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/pdata-quirks.c | 37
source 'dpi.0'
Changes compared to previous version:
- rebased on next-20140122 from next-20140115
- using omap36xx.dtsi instead of unsupported 1ghz omap37xx100
Christoph Fritz (5):
ARM: dts: omap3: Add support for INCOstartec a83x module
ARM: dts: omap3: Add support for INCOstartec DBB056
INCOstartec LILLY-DBB056 is a carrier board (baseboard) for
computer-on-module LILLY-A83X.
This patch adds device-tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-lilly
INCOstartec LILLY-A83X module is a TI DM3730xx100 (OMAP3) SoC
computer-on-module.
This patch adds device tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 445 +++
1 file
Full device tree support for omapdss is not yet accomplished. Until
then, init display by legacy platform code.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/dss-common.c | 49
arch/arm/mach-omap2/dss-common.h |1
Full device tree support for clock control is not yet accomplished. Until
then, configure the 24Mhz of sys_clkout2 to feed an USB-Hub here.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/pdata-quirks.c | 37
1 file changed
DBB056 doesn't use DSI for its display, but omap3 forces this
erroneously for all its boards:
| OMAP DSS rev 2.0
| omapdss DPI error: can't get VDDS_DSI regulator
| omapfb omapfb: failed to connect default display
| omapfb omapfb: failed to init overlay connections
| omapfb omapfb:
maximum 800 MHz.
For more info, see Datasheet http://www.ti.com/lit/ds/sprs685d/sprs685d.pdf
section 7.2.1 Device and Development-Support Tool Nomenclature.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap37xx100.dtsi | 44
1
Full device tree support for clock control is not yet accomplished. Until
then, configure the 24Mhz of sys_clkout2 to feed an USB-Hub here.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/pdata-quirks.c | 37
1 file changed
INCOstartec LILLY-A83X module is a TI DM3730xx100 (OMAP3) SoC
computer-on-module.
This patch adds device-tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 441 +++
1 file
Full device tree support for omapdss is not yet accomplished. Until
then, init display by legacy platform code.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/dss-common.c | 49
arch/arm/mach-omap2/dss-common.h |1
INCOstartec LILLY-DBB056 is a carrier board (baseboard) for
computer-on-module LILLY-A83X.
This patch adds device-tree support for most of its features.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-lilly
This set of patches adds board support for an omap3 system from INCOstartec.
It's based on next-20140115.
Christoph Fritz (6):
ARM: dts: Add CPU OPP table for omap37xx100
ARM: dts: omap3: Add support for INCOstartec a83x module
ARM: dts: omap3: Add support for INCOstartec DBB056 baseboard
DBB056 doesn't use DSI for its display, but omap3 forces this erroneously:
| OMAP DSS rev 2.0
| omapdss DPI error: can't get VDDS_DSI regulator
| omapfb omapfb: failed to connect default display
| omapfb omapfb: failed to init overlay connections
| omapfb omapfb: failed to setup omapfb
Hi,
I'm having here a custom am335x board with DDR3 equipped trying to
setup suspend/resume support. I have tested this with the ancient
TI-PSP-3.2 Kernel and current 3.13-rc plus some pm patches.
Problem: After suspending the device, it doesn't resume (freeze):
echo mem /sys/power/state
[
On Thu, 2013-12-05 at 14:42 +0100, Christoph Fritz wrote:
Hi,
I'm having here a custom am335x board with DDR3 equipped trying to
setup suspend/resume support. I have tested this with the ancient
TI-PSP-3.2 Kernel and current 3.13-rc plus some pm patches.
Problem: After suspending
On Thu, 2013-04-18 at 18:26 -0500, Jon Hunter wrote:
On 04/18/2013 06:24 PM, Jon Hunter wrote:
To get the values right for dt-GPMC-NAND-Config, here are the GPMC
config registers for chip-select 0, they are taken from u-boot
by doing md 0x6E60 7 on the u-boot shell:
On Fri, 2013-04-19 at 11:01 +0200, Christoph Fritz wrote:
This is how u-boot GPMC config differs from final kernel configuration:
u-boot: GPMC_CONFIG1: 0x6e60: 0x1800
kernel: 0x1800
u-boot: GPMC_CONFIG2: 0x6e64: 0x00141400
On Fri, 2013-04-19 at 07:57 -0500, Jon Hunter wrote:
On 04/19/2013 04:01 AM, Christoph Fritz wrote:
I think you need to convert the register settings to ns and put those
values in the dts file.
yes, I already did so. Please see my last mail.
--
To unsubscribe from this list: send the line
On Fri, 2013-04-19 at 09:00 -0500, Jon Hunter wrote:
On 04/19/2013 07:02 AM, Christoph Fritz wrote:
so I hacked the missing values to omap2_nand_gpmc_retime():
From 8868823925441a824fe0d3143614482f25fb379b Mon Sep 17 00:00:00 2001
From: Christoph Fritz chf.fr...@googlemail.com
Date
, this
patch also adds oe_on and we_on to nand_default_timings[] as they
would be by the retime function.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/board-flash.c |3 +++
arch/arm/mach-omap2/gpmc-nand.c | 40 +
2 files
/omap2/dss/dpi.c:201: error: implicit declaration of function
‘dsi_get_pll_clkin’
drivers/video/omap2/dss/dpi.c:212: error: implicit declaration of function
‘dsi_pll_calc’
Enabling OMAP2_DSS_DSI fixes this. This is my proposed patch. You may be want
to merge it?
From: Christoph Fritz chf.fr
On Thu, 2013-04-18 at 12:21 +0300, Tomi Valkeinen wrote:
On 2013-04-18 12:09, Tomi Valkeinen wrote:
On 2013-04-18 11:37, Christoph Fritz wrote:
With linux-next this patch breaks compiling here because DPI now depends
on DSI - but my omap3 board here doesn't use DSI at all:
drivers
On Thu, 2013-04-18 at 17:37 +0300, Tomi Valkeinen wrote:
But here with linux-next (in contrast to 3.9-rc) removing all regulator
dependencies from drivers/video/omap2/dss/dpi.c does not make the trick.
The display stays dark :-( ...
That's with your DT hacked kernel, right? Not the
Hi
I'm trying to setup nand support for an omap3 board for linux-next
(next-20130417). This is my approach so far:
+gpmc {
+ ranges = 0 0 0x3000 0x100;
+ nand@0,0 {
+ reg = 0 0 0xff; /* - ? not sure about that */
+ nand-bus-width = 16;
+
Hi Jon
On Thu, 2013-04-18 at 14:39 -0500, Jon Hunter wrote:
On 04/18/2013 02:03 PM, Christoph Fritz wrote:
I had put the complete size in here so ...
+ reg = 0 0 0x100;
Thanks.
+ nand-bus-width = 16;
+ ti,nand-ecc-opt = bch8
On Thu, 2013-04-18 at 17:28 -0500, Jon Hunter wrote:
On 04/18/2013 03:23 PM, Christoph Fritz wrote:
OMAP3_EVM # md 0x6E60 7
6e60: 1800 00141400 00141400 0f010f01
6e70: 010c1414 1f0f0a80 0870 p...
I don't see any other errors
On Mon, 2013-04-15 at 13:20 +0300, Grygorii Strashko wrote:
On 04/13/2013 09:27 PM, Christoph Fritz wrote:
Hi
while testing an omap3 board with device tree support I stumbled upon a
bug which is due to wrong initialization order of twl-core and
twl-regulator (I suppose): In the boot
until pin control probing before
GPIO driver probing.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
drivers/net/ethernet/smsc/smsc911x.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/net/ethernet/smsc/smsc911x.c
b/drivers/net/ethernet/smsc/smsc911x.c
This patch adds GPIO pins found on AM/DM37x.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/mach-omap2/mux34xx.h |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/mux34xx.h b/arch/arm/mach-omap2/mux34xx.h
index 6543ebf..3f26d29
On Mon, 2013-04-01 at 22:05 +0200, Javier Martinez Canillas wrote:
On Mon, Apr 1, 2013 at 6:41 PM, Christoph Fritz
As a quick-fix (hack) I wrote directly to the registers in gpio_probe()
to enable GPIO banks. I now geht this:
[0.214630] omap_gpio_probe, 1133, CM_CLKSEL_PER 0x48005040
Hi
while testing an omap3 board with device tree support I stumbled upon a
bug which is due to wrong initialization order of twl-core and
twl-regulator (I suppose): In the boot process they get loaded way too
late so that a lot of drivers before where configured wrong or just
refuse to load.
On Sat, 2013-04-13 at 20:30 +0200, Javier Martinez Canillas wrote:
On Sat, Apr 13, 2013 at 7:42 PM, Christoph Fritz
chf.fr...@googlemail.com wrote:
Yes, my last approach to solve the IRQ flags not saved on the
IORESOURCE_IRQ struct resource issue is to add a new
irq_get_trigger_type
On Mon, 2013-04-01 at 22:05 +0200, Javier Martinez Canillas wrote:
As a quick-fix (hack) I wrote directly to the registers in gpio_probe()
to enable GPIO banks. I now geht this:
[0.214630] omap_gpio_probe, 1133, CM_CLKSEL_PER 0x48005040:
0x00ff
[0.214660]
Hi Javier
On Sat, 2013-03-30 at 14:18 +0100, Javier Martinez Canillas wrote:
A call to gpio_request() to enable the GPIO bank is needed before
using a GPIO as an IRQ source, otherwise accesses to the GPIO bank
registers fails making the kernel to hang.
Yes, that is exactly my problem here.
This patch sets gpio #interrupt-cells from a falsely acquired '1' to '2'
referring to Documentation/devicetree/bindings/gpio/gpio-omap.txt:
The first cell is the GPIO number.
The second cell is used to specify flags:
bits[3:0] trigger type and level flags:
1 =
On Thu, 2013-03-28 at 09:38 -0700, Tony Lindgren wrote:
* Christoph Fritz chf.fr...@googlemail.com [130328 01:12]:
- Fix 'function-mask' referring to TRM Section 7.4.4:
Pad Functional Multiplexing and Configuration.
- Fix 'omap3_pmx_core' referring to TRM Table 7-4:
Core Control
On Fri, 2013-03-29 at 10:37 +0100, Christoph Fritz wrote:
On Thu, 2013-03-28 at 09:38 -0700, Tony Lindgren wrote:
* Christoph Fritz chf.fr...@googlemail.com [130328 01:12]:
- Fix 'function-mask' referring to TRM Section 7.4.4:
Pad Functional Multiplexing and Configuration.
- Fix
- Fix 'function-mask' referring to TRM (Omap 36xx) Section 13.4.4:
Pad Functional Multiplexing and Configuration.
- Fix 'omap3_pmx_wkup' referring to TRM Table 13-6:
Wkup Control Module Pad Configuration Register Fields.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch
Configuration Register Fields.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
arch/arm/boot/dts/omap3.dtsi | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 1acc261..6ce3b5c 100644
--- a/arch
On Wed, 2010-05-12 at 11:29 -0700, Dmitry Torokhov wrote:
On Wed, May 12, 2010 at 07:15:22PM +0100, Jonathan Cameron wrote:
Hi,
I was wondering if you could provide a bit more detail on what this
driver is actually doing? My appologies if I have missed a
previous explanation. If so,
74 matches
Mail list logo
