[PATCH] Staging: TIDSPBRIDGE: Remove UUID helper

From: Ivaylo Dimitrov freemangor...@abv.bg Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't need to be exported. It can also be made way simpler by using sscanf. Signed-off-by: Ivaylo Dimitrov freemangor...@abv.bg --- drivers/staging/tidspbridge/Makefile

[PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

From: Ivaylo Dimitrov freemangor...@abv.bg This fixes the following bug: Bug Report source file: drivers/staging/tidspbridge/rmgr/drv_interface.c issue : mapping of physical memory without address range checks 259 static int bridge_mmap(struct file *filp, struct vm_area_struct

Re: [BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet length 3149594624

On 14.02.2014 19:11, Ivaylo Dimitrov wrote: On 14.02.2014 18:24, Will Deacon wrote: You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line above. This seems to fix the issue too, but I am afraid

Re: [BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet length 3149594624

Hi, On 14.02.2014 18:24, Will Deacon wrote: You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line above. the following patch diff --git a/drivers/net/wireless/ti/wl1251/rx.c

[PATCH] wl1251: use skb_trim to make skb shorter

the current code is directly setting skb-len, which is not correct and brings problems with HAVE_EFFICIENT_UNALIGNED_ACCESS enabled in config Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/net/wireless/ti/wl1251/rx.c |2 +- 1 file changed, 1 insertion(+), 1 deletion

Re: [PATCH v2] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

On 10.01.2014 12:56, Tomi Valkeinen wrote: On 2014-01-05 15:13, Ivaylo Dimitrov wrote: From: Ivaylo Dimitrov freemangor...@abv.bg Commit c37dd677988ca50bc8bc60ab5ab053720583c168 fixes the unbalanced unlock in acx565akm_enable but introduces another problem - if acx565akm_panel_power_on exits

[PATCH] OMAPDSS: DISPC: Fix 34xx overlay scaling calculation

From: Ivaylo Dimitrov freemangor...@abv.bg commit 7faa92339bbb1e6b9a80983b206642517327eb75 OMAPDSS: DISPC: Handle synclost errors in OMAP3 introduces limits check to prevent SYNCLOST errors on OMAP3. However, it misses the logic found in Nokia kernels that is needed to correctly calculate whether

[PATCH] iio: tsl2563: Initialize channels

From: Ivaylo Dimitrov freemangor...@abv.bg Correctly initialize device channels, otherwise writing the calibration values to sysfs nodes does not work Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/iio/light/tsl2563.c |6 -- 1 files changed, 4 insertions(+), 2

Re: [PATCH] iio: tsl2563: Initialize channels

On 12.01.2014 22:55, Peter Meerwald wrote: I think the fix should rather be if (chan-channel2 == IIO_MOD_LIGHT_BOTH) chip-calib0 = calib_from_sysfs(val); else if (chan-channel2 == IIO_MOD_LIGHT_IR) chip-calib1 = calib_from_sysfs(val);

[PATCH v2] OMAPDSS: DISPC: Fix 34xx overlay scaling calculation

From: Ivaylo Dimitrov freemangor...@abv.bg commit 7faa92339bbb1e6b9a80983b206642517327eb75 OMAPDSS: DISPC: Handle synclost errors in OMAP3 introduces limits check to prevent SYNCLOST errors on OMAP3. However, it misses the logic found in Nokia kernels that is needed to correctly calculate whether

[PATCH] iio: tsl2563: Use the correct channel2 member

From: Ivaylo Dimitrov freemangor...@abv.bg Use the correct channel2 member instead of channel when dealing with sysfs reads/writes Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/iio/light/tsl2563.c | 16 ++-- 1 files changed, 10 insertions(+), 6 deletions

[BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet length 3149594624

Since next-21012014 I started to receive Received disconnect from x.x.x.x: 2: Bad packet length 3149594624 errors when trying to establish ssh session over wifi to my N900, running Maemo 5. I bisected and it turned out that commit dce5c9e35bc4085bd33eccdb8c9ec5a643507a14 ARM: 7928/1: kconfig:

Re: [BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet length 3149594624

On 13.02.2014 20:21, Will Deacon wrote: That's certainly unexpected. The n900 has (iirc) a Cortex-A8, which as an ARMv7 core, can perform unaligned accesses to normal, cacheable memory in hardware. Yep, Cortex-A8 and it has no problem to do unaligned memory accesses AFAIK. I suspect it is

Re: [BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet length 3149594624

On 13.02.2014 21:29, Will Deacon wrote: Can you try hacking crypto/memneq.c so that it doesn't use CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS please? That would at least point the finger at net/mac80211/rx.c or similar. Cheers, Will Well, I am lazy so I hacked net/mac80211/rx.c first: index

Re: [BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet length 3149594624

On 14.02.2014 18:24, Will Deacon wrote: You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line above. This seems to fix the issue too, but I am afraid there is more to be done, as I see Feb 14

[PATCH] of/base: Replace alias if it already exists

The current code unconditionally adds aliases without check if it already exists, so it is not possible to alter an alias, from board DT file for example. Fix that by replacing an alias if it already exists Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/of/base.c | 34

Re: [PATCH] of/base: Replace alias if it already exists

On 2.06.2014 17:59, Grant Likely wrote: On Sun, 1 Jun 2014 15:01:23 +0300, Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com wrote: The current code unconditionally adds aliases without check if it already exists, so it is not possible to alter an alias, from board DT file for example. Fix

Re: [PATCH] of/base: Replace alias if it already exists

On 3.06.2014 11:53, Grant Likely wrote: So, if I understand correctly, the .dtsi file sets up aliases like so: aliases { i2c0 = i2c1; i2c1 = i2c2; i2c2 = i2c3; i2c3 = i2c4; i2c4 = i2c5; }; and the board file does this: aliases { i2c1 =

Re: [PATCH] of/base: Replace alias if it already exists

On 3.06.2014 12:58, Ivaylo Dimitrov wrote: On 3.06.2014 11:53, Grant Likely wrote: [...] Can you try putting the following into your board dts file and see if it works? aliases { i2c0;/* Deactivate the old alias by making it blank */ i2c1 = i2c1; i2c2 = i2c2

Re: Re: [PATCH] ARM: OMAP2+: Add support for thumb mode on DT booted N900

Hi, On 5.02.2014 19:17, Sebastian Reichel wrote: Hi, On Wed, Feb 05, 2014 at 05:38:54PM +0100, Pali Rohár wrote: I assumed, that the workaround is not needed for this device type. That rx51 secure call must not be called on non secure devices (e.g. qemu), because it cause kernel crash. So

OMAPDSS: DISPC: horizontal timing too tight errors

Hi, commit 7faa92339bbb1e6b9a80983b206642517327eb75 OMAPDSS: DISPC: Handle synclost errors in OMAP3 introduces some limits check to prevent SYNCLOST errors on OMAP3 in a specific usecase. The problem I see here (on Nokia N900, Maemo 5, linux 3.13-rc6, DSP accel video decoding) is that those

Re: OMAPDSS: DISPC: horizontal timing too tight errors

On 07.01.2014 20:05, Pavel Machek wrote: On Tue 2014-01-07 14:35:02, Tomi Valkeinen wrote: On 2014-01-06 11:43, Ivaylo Dimitrov wrote: Hi, commit 7faa92339bbb1e6b9a80983b206642517327eb75 OMAPDSS: DISPC: Handle synclost errors in OMAP3 introduces some limits check to prevent SYNCLOST errors

Re: OMAPDSS: DISPC: horizontal timing too tight errors

On 07.01.2014 14:35, Tomi Valkeinen wrote: On 2014-01-06 11:43, Ivaylo Dimitrov wrote: Hi, commit 7faa92339bbb1e6b9a80983b206642517327eb75 OMAPDSS: DISPC: Handle synclost errors in OMAP3 introduces some limits check to prevent SYNCLOST errors on OMAP3 in a specific usecase. The problem I see

[BISECTED] OMAP: DSS: clk rate mismatch

Hi Tomi, 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] [ cut here ] [0.624298] WARNING: CPU:

Re: [BISECTED] OMAP: DSS: clk rate mismatch

On 28.01.2014 10:48, Tomi Valkeinen wrote: I made a somewhat hacky quickfix for beagle. Applying that and the clk-divider from the link above makes things work for me. However, as I said, the issue with n900 might be different, but it'd be interesting to hear if it has any effect. Tomi

Re: [BISECTED] OMAP: DSS: clk rate mismatch

On 29.01.2014 11:10, Tero Kristo wrote: It looks like the omap36xx version of the omap96m_alwon_fck is modelled improperly in the dts files. I don't have access to omap36xx hardware myself, but give a try for the following patch: It could be that 36xx omap96m_alwon_fck clock is wrongly

Re: [BISECTED] OMAP: DSS: clk rate mismatch

On 29.01.2014 13:30, Tomi Valkeinen wrote: On 2014-01-28 20:17, Ivaylo Dimitrov wrote: On 28.01.2014 10:48, Tomi Valkeinen wrote: I made a somewhat hacky quickfix for beagle. Applying that and the clk-divider from the link above makes things work for me. However, as I said, the issue

[PATCH v3] Staging: TIDSPBRIDGE: Remove UUID helper

From: Ivaylo Dimitrov freemangor...@abv.bg Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't need to be exported. It can also be made way simpler by using sscanf. Signed-off-by: Ivaylo Dimitrov freemangor...@abv.bg --- drivers/staging/tidspbridge/Makefile

Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

On 11.12.2013 10:33, Dan Carpenter wrote: On Wed, Dec 11, 2013 at 09:45:52AM +0200, Ivajlo Dimitrov wrote: I can pick your changes and re-send the original patch with them incorporated if there are no objections. Are you fine with that? Do it on top of staging-next, don't redo the original.

[PATCH] Staging: TIDSPBRIDGE: Fix mmap to map the correct region of physical memory

before calling vm_iomap_memory() and adding it back afterwards. Reported-by: Dheeraj CVR cvr.dhee...@gmail.com Signed-off-by: Ivaylo Dimitrov freemangor...@abv.bg --- drivers/staging/tidspbridge/rmgr/drv_interface.c | 30 +--- 1 file changed, 27 insertions(+), 3 deletions

[PATCH v2] Staging: tidspbridge: Use hashtable implementation

From: Ivaylo Dimitrov freemangor...@abv.bg Use upstream hashtable implementation instead of generic code Signed-off-by: Ivaylo Dimitrov freemangor...@abv.bg --- drivers/staging/tidspbridge/gen/gh.c | 141 +++- drivers/staging/tidspbridge/include/dspbridge/gh.h

Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator

On 27.12.2013 11:48, Pavel Machek wrote: On Thu 2013-12-26 01:12:39, Ivaylo Dimitrov wrote: From: Ivaylo Dimitrov freemangor...@abv.bg On memory limited devices, CMA fails easily when asked to allocate big chunks of memory like framebuffer memory needed for video playback. Add boot parameter

[PATCH] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

From: Ivaylo Dimitrov freemangor...@abv.bg Commit c37dd677988ca50bc8bc60ab5ab053720583c168 fixes the unbalanced unlock in acx565akm_enable but introduces another problem - if acx565akm_panel_power_on exits early, the mutex is not unlocked. Fix that by unlocking the mutex on early return. Also add

Re: [PATCH] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

On 04.01.2014 14:51, Pavel Machek wrote: On Mon 2013-12-30 18:17:52, Ivaylo Dimitrov wrote: From: Ivaylo Dimitrov freemangor...@abv.bg Commit c37dd677988ca50bc8bc60ab5ab053720583c168 fixes the unbalanced unlock in acx565akm_enable but introduces another problem - if acx565akm_panel_power_on

[PATCH v2] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

From: Ivaylo Dimitrov freemangor...@abv.bg Commit c37dd677988ca50bc8bc60ab5ab053720583c168 fixes the unbalanced unlock in acx565akm_enable but introduces another problem - if acx565akm_panel_power_on exits early, the mutex is not unlocked. Fix that by unlocking the mutex on early return. Also add

[PATCH v2] Staging: tidspbridge: Use hashtable implementation

From: Ivaylo Dimitrov freemangor...@abv.bg Use upstream hashtable implementation instead of generic code Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/staging/tidspbridge/gen/gh.c | 148 drivers/staging/tidspbridge/include/dspbridge

Re: [PATCH v2] Staging: tidspbridge: Use hashtable implementation

On 05.01.2014 21:47, Dan Carpenter wrote: Looks much nicer. I had a few tiny comments, but those could be addressed in later patches. (There is a lot of work to be done on this driver). On Sun, Jan 05, 2014 at 08:58:12PM +0200, Ivaylo Dimitrov wrote: -static u16 name_hash(void *key, u16

[PATCH v3] Staging: tidspbridge: Use hashtable implementation

From: Ivaylo Dimitrov freemangor...@abv.bg Use upstream hashtable implementation instead of generic code Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/staging/tidspbridge/gen/gh.c | 148 drivers/staging/tidspbridge/include/dspbridge

[PATCH v2] Staging: TIDSPBRIDGE: Remove UUID helper

From: Ivaylo Dimitrov freemangor...@abv.bg Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't need to be exported. It can also be made way simpler by using sscanf. Signed-off-by: Ivaylo Dimitrov freemangor...@abv.bg --- drivers/staging/tidspbridge/Makefile

[PATCH] Staging: tidspbridge: Use hashtable implementation

From: Ivaylo Dimitrov freemangor...@abv.bg Use upstream hashtable implementation instead of generic code Signed-off-by: Ivaylo Dimitrov freemangor...@abv.bg --- drivers/staging/tidspbridge/gen/gh.c | 141 +++- drivers/staging/tidspbridge/include/dspbridge/gh.h

[PATCH] ARM: omapfb: Add early framebuffer memory allocator

From: Ivaylo Dimitrov freemangor...@abv.bg On memory limited devices, CMA fails easily when asked to allocate big chunks of memory like framebuffer memory needed for video playback. Add boot parameter omapfb_memsize which allocates memory to be used as dma coherent memory, so dma_alloc_attrs

Re: BUG: usb: obex in g_nokia.ko causing kernel panic

Hi Felipe, cool, I'll send this during the -rc and Cc stable, then I'll manually backport it to stable later. PING! I still do not see this patch in linus tree. What happened? -- Pali Rohár pali.ro...@gmail.com BUMP Is there any problem with above patch? If you are short on time or

[PATCH] usb: musb: Fix obex in g_nokia.ko causing kernel panic

dump is from 3.12-rc5 kernel Reported-by: Pali Rohár pali.ro...@gmail.com Signed-off-by: Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com --- drivers/usb/musb/omap2430.c |2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c index 2a408cd..8aa59a2

Re: [RFC] adp1653: Add device tree bindings for LED controller

Hi, Can you capture raw bayer images correctly? I assume green means YUV buffers that are all zero. Do you know more specifically which patch breaks it? CCing freemangordon (Ivaylo Dimitrov). He tried to debug it months ago but without success. Should know more info about this problem. I

Re: N900 modem support in 3.18-rc1

On 13.11.2014 18:24, Pavel Machek wrote: On Fri 2014-11-07 09:04:52, Ivaylo Dimitrov wrote: Sebastian is quiet, can we have the patch? :-). Sure, why not :) https://gitorious.org/linux-n900/freemangordons-linux-n900/commits/30e9a5c498a89cea4c29523f69e436bf0af3c631 commits 89ce13b, b81d80d

Re: N900 modem support in 3.18-rc1

On 7.11.2014 01:01, Pali Rohár wrote: For voice calls you need: * kernel driver cmt-speech (or it has some new name) * cmt-speech userspace library (communication with kernel) * pulseaudio modules which are using that library Freemangordon (Ivaylo Dimitrov, CCed) should know more about

Re: N900 modem support in 3.18-rc1

On 14.11.2014 19:20, Sebastian Reichel wrote: The patch looks ok. It does not cleanup the cmt-speech driver for mainline usage, but it should work. Before adding this driver to the mainline kernel there should be open source userspace support anyway. I am aware of that(patch not ready),

Re: wl1251: NVS firmware data

On 8.12.2014 21:26, Dan Williams wrote: a) change driver to prefer a new wl1251-nvs-n900.bin file, but fall back to wl1251-nvs.bin if the first one isn't present b) have a wl1251-cal-nvs-update service that, if wl1521-nvs-n900.bin is *not* present mounts the CAL MTD, reads the data, writes

Re: [PATCH] usb: gadget: nokia: Add mass storage driver to g_nokia

On 2.02.2015 21:14, Felipe Balbi wrote: On Mon, Feb 02, 2015 at 08:07:51PM +0100, Pali Rohár wrote: On Monday 02 February 2015 20:01:11 Felipe Balbi wrote: Hi, On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote: On Monday 02 February 2015 19:54:58 Felipe Balbi wrote: Hi, On Sat,

Re: [PATCH] usb: gadget: nokia: Add mass storage driver to g_nokia

Hi, On 7.02.2015 20:01, Ivaylo Dimitrov wrote: On 2.02.2015 21:14, Felipe Balbi wrote: On Mon, Feb 02, 2015 at 08:07:51PM +0100, Pali Rohár wrote: On Monday 02 February 2015 20:01:11 Felipe Balbi wrote: Hi, On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote: On Monday 02

Re: linux 4.2-rc1 broken Nokia N900

On 24.07.2015 11:18, Dave Young wrote: Pali, could you tell how do you test mainline kernel on n900? I used to use n900 as a usb dbgp gadget with a backport patch to 2.6.28 so that I can get early debug kernel message from my laptop. I tried mainline previously with Fedora arm, text mode

[PATCH] input: gpio_keys: Fix check for disabling unsupported key

ect verify logic. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- drivers/input/keyboard/gpio_keys.c | 28 +++- 1 file changed, 19 insertions(+), 9 deletions(-) diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys

Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator

Hi Tomi, On 4.01.2016 13:37, Tomi Valkeinen wrote: We probably need exactly the same for omapdrm, as omapfb is on the way to being deprecated. And sounds to me that we probably need similar for other devices which try to do large allocations (camera? video decoders?). Re omapdrm - I guess

Re: [PATCH] input: gpio_keys: Fix check for disabling unsupported key

Hi, On 5.01.2016 03:19, Dmitry Torokhov wrote: /* First validate */ - for (i = 0; i < ddata->pdata->nbuttons; i++) { - struct gpio_button_data *bdata = >data[i]; + for (i = 0; i < n_events; i++) { for_each_set_bit()? Yeah, seems I must have overslept that

[PATCH] power_suply: isp1704_charger: Fix isp1704_write() definition

All calls to isp1704_write() are using parameter sequence of isp1704_write(isp, reg, val) but the function is defined as isp1704_write(isp, val, reg). Fix isp1704_write function definition so that the driver to be functional. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.

Re: [PATCH] power_suply: isp1704_charger: Fix isp1704_write() definition

Hi Pali, On 1.01.2016 13:26, Pali Rohár wrote: On Friday 01 January 2016 12:03:29 Ivaylo Dimitrov wrote: All calls to isp1704_write() are using parameter sequence of isp1704_write(isp, reg, val) but the function is defined as isp1704_write(isp, val, reg). Fix isp1704_write function definition

Re: [PATCH 2/2] OMAP: RX51: save ATAGS data in the early boot stage

Hi, On 24.12.2015 20:56, Tony Lindgren wrote: Maybe update the description to say "This fixes a regression with device tree based booting compared to legacy booting for n900 to make the n900 legacy user space to also work with device tree based booting". OK, will do. It would be nice to

Re: [PATCH v2] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

On 29.12.2015 09:46, Tomi Valkeinen wrote: Oh, I'm sorry, I must have forgotten about that. Please, send a new patch. Tomi Actually it is me to be sorry for making noise, I've missed 0eb0dafb674cd6bfac2e3204b2f8b907e26b1138 with all those patches moving files around. Ivo -- To

Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry

Hi, On 15.12.2015 14:20, Russell King - ARM Linux wrote: You could also just save_atags() in there, with a comment saying that this is a work-around for N900 which needs the ATAGs saved, and this is allowed in ->reserve as a special exception. What about this (just to confirm I got the idea

Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator

On 26.12.2013 01:12, Ivaylo Dimitrov wrote: From: Ivaylo Dimitrov <freemangor...@abv.bg> On memory limited devices, CMA fails easily when asked to allocate big chunks of memory like framebuffer memory needed for video playback. Add boot parameter "omapfb_memsize" which

Re: [PATCH v2] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

Hi Tomi, On 13.01.2014 12:20, Tomi Valkeinen wrote: On 2014-01-11 11:39, Ivaylo Dimitrov wrote: The patch does not apply cleanly on top of rc7, however I applied it by hand. So far it seems it fixes the issue brought by c37dd677988ca50bc8bc60ab5ab053720583c168, though I didn't test

Re: [PATCH 1/2] ARM: ATAGS: move save_atags() to include/asm arch/arm/include/asm/setup.h

On 24.12.2015 20:53, Tony Lindgren wrote: * Pali Rohár <pali.ro...@gmail.com> [151224 09:48]: On Thursday 24 December 2015 17:37:55 Ivaylo Dimitrov wrote: So it can be used by code outside arch/arm/kernel/. Fix save_atags() declaration to match its definition while at it. Sign

[PATCH 2/2] OMAP: RX51: save ATAGS data in the early boot stage

Nokia N900 (RX51) legacy userspace needs various ATAGS passed by the bootloader (boot reason, device serial, boot mode, various GPIO swithes, etc). Save that data early enough in the boot process, so it can be exported later in /proc/atags Signed-off-by: Ivaylo Dimitrov <ivo.g.dimit

[PATCH 0/2] OMAP: RX51: save atags data to be exported on /proc/atags

Nokia N900 legacy userspace needs ATAGS passed by the bootloder to be available in /proc/atags. With DT booted kernel this information is no longer availabe. Fix that by saving ATAGS data early in the boot stage so it can be exported in /proc/atags later Ivaylo Dimitrov (2): ARM: ATAGS: move

[PATCH 1/2] ARM: ATAGS: move save_atags() to include/asm arch/arm/include/asm/setup.h

So it can be used by code outside arch/arm/kernel/. Fix save_atags() declaration to match its definition while at it. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/include/asm/setup.h | 6 ++ arch/arm/kernel/atags.h | 6 -- 2 files changed, 6 inse

[PATCH 1/3] ARM: ATAGS: move atags.h to include/asm so it can be included by files outside kernel/

This is needed by a follow-up patch that saves atags on RX51 device Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/include/asm/atags.h | 20 arch/arm/kernel/atags.h | 20 arch/arm/kernel/atags_parse.c | 3 +-- ar

[PATCH 2/3] ARM: ATAGS: Fix declaration of function save_atags

In file atags_proc.c function save_atags() expect const argument, but in atags.h file is declarated as non const. Fix declaration in atags.h file to match what is expected. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/include/asm/atags.h | 4 ++-- 1 file chan

[PATCH 3/3] OMAP: RX51: save ATAGS data in the early boot stage

Nokia N900 (RX51) legacy userspace needs various ATAGS passed by the bootloader (boot reason, device serial, boot mode, various GPIO swithes, etc). Save that data early enough in the boot process, so it can be exported later in /proc/atags Signed-off-by: Ivaylo Dimitrov <ivo.g.dimit

[PATCH 0/3] OMAP: RX51: save atags data to be exported on /proc/atags

Nokia N900 legacy userspace needs ATAGS passed by the bootloder to be available in /proc/atags. With DT booted kernel this information is no longer availabe. Fix that by saving ATAGS data early in the boot stage so it can be exported in /proc/atags later Ivaylo Dimitrov (3): ARM: ATAGS: move

Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry

On 26.11.2015 22:39, Tony Lindgren wrote: Just to explore options.. How about make a minimal device driver that just loads the atags blob from /lib/firmware and then shows it in /proc/atags? Of course some checking on the atags should be done by the driver.. What is the chance for such a

Re: dma_declare_coherent_memory fails for RAM allocated memory

On 2.06.2016 20:14, Ivaylo Dimitrov wrote: Hi, On 1.06.2016 14:18, Brian Starkey wrote: Hi Ivo, On Sun, May 29, 2016 at 05:56:02PM +0300, Ivaylo Dimitrov wrote: Hi, When trying to declare and use DT reserved memory region on ARM (OMAP3), dma_declare_coherent_memory() fails in memremap

[PATCH v2 0/2] media: add et8ek8 camera sensor driver and documentation

This series adds driver for Toshiba et8ek8 camera sensor found in Nokia N900 Changes from v2: - driver and documentation split into separate patches - removed custom controls - code changed according to the comments on v1 Ivaylo Dimitrov (2): media: Driver for Toshiba et8ek8 5MP sensor

[PATCH v2 2/2] media: et8ek8: Add documentation

Add DT bindings description Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- .../bindings/media/i2c/toshiba,et8ek8.txt | 50 ++ 1 file changed, 50 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.txt

[PATCH v2 1/2] media: Driver for Toshiba et8ek8 5MP sensor

The sensor is found in Nokia N900 main camera Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- drivers/media/i2c/Kconfig|1 + drivers/media/i2c/Makefile |1 + drivers/media/i2c/et8ek8/Kconfig |6 + drivers/media/i2c/

Re: [PATCH 1/1] v4l: Add camera voice coil lens control class, current control

Hi, On 12.06.2016 23:41, Sakari Ailus wrote: From: Sakari Ailus Add a V4L2 control class for voice coil lens driver devices. These are simple devices that are used to move a camera lens from its resting position. Signed-off-by: Sakari Ailus

Re: [PATCH 5/7] ARM: OMAP: dmtimer: Do not call PM runtime functions when not needed.

On 10.06.2016 13:22, Tony Lindgren wrote: OK. And I just applied the related dts changes. Please repost the driver changes and DT binding doc with Rob's ack to the driver maintainers to apply. Already did, see https://lkml.org/lkml/2016/5/16/429 Shall I do anything else? Thanks, Ivo

[PATCH v3 0/2] media: add et8ek8 camera sensor driver and documentation

This series adds driver for Toshiba et8ek8 camera sensor found in Nokia N900 Changes from v2: - fix build when CONFIG_PM is not defined Changes from v1: - driver and documentation split into separate patches - removed custom controls - code changed according to the comments on v1 Ivaylo

[PATCH v3 1/2] media: Driver for Toshiba et8ek8 5MP sensor

The sensor is found in Nokia N900 main camera Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- drivers/media/i2c/Kconfig|1 + drivers/media/i2c/Makefile |1 + drivers/media/i2c/et8ek8/Kconfig |6 + drivers/media/i2c/

[PATCH v3 2/2] media: et8ek8: Add documentation

Add DT bindings description Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- .../bindings/media/i2c/toshiba,et8ek8.txt | 50 ++ 1 file changed, 50 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.txt

Re: [PATCH 5/7] ARM: OMAP: dmtimer: Do not call PM runtime functions when not needed.

Hi, On 13.06.2016 10:10, Tony Lindgren wrote: * Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> [160610 14:23]: On 10.06.2016 13:22, Tony Lindgren wrote: OK. And I just applied the related dts changes. Please repost the driver changes and DT binding doc with Rob's ack to the

Re: [PATCH 0/7] ir-rx51 driver fixes

Hi, On 13.06.2016 21:17, Pali Rohár wrote: On Saturday 07 May 2016 17:21:41 Ivaylo Dimitrov wrote: ir-rx51 is a driver for Nokia N900 IR transmitter. The current series fixes the remaining problems in the driver: - replace GP timer 9 with PWM framework usage - replace pulse width timer

Re: [PATCH] userspace API definitions for auto-focus coil

Hi, On 5.06.2016 22:07, Pavel Machek wrote: Add userspace API definitions. Signed-off-by: Pavel Machek diff --git a/include/uapi/linux/v4l2-controls.h b/include/uapi/linux/v4l2-controls.h index b6a357a..23011cc 100644 --- a/include/uapi/linux/v4l2-controls.h +++

Re: [PATCHv3] support for AD5820 camera auto-focus coil

On 24.05.2016 23:20, Pavel Machek wrote: Hi! devm_regulator_get()? I'd rather avoid devm_ here. Driver is simple enough to allow it. Now thinking about it, what would happen here if regulator_get() returns -EPROBE_DEFER? Wouldn't it be better to move regulator_get to the probe()

Re: dma_declare_coherent_memory fails for RAM allocated memory

Hi, On 1.06.2016 14:18, Brian Starkey wrote: Hi Ivo, On Sun, May 29, 2016 at 05:56:02PM +0300, Ivaylo Dimitrov wrote: Hi, When trying to declare and use DT reserved memory region on ARM (OMAP3), dma_declare_coherent_memory() fails in memremap(). This is from today's master

dma_declare_coherent_memory fails for RAM allocated memory

Hi, When trying to declare and use DT reserved memory region on ARM (OMAP3), dma_declare_coherent_memory() fails in memremap(). This is from today's master: [ cut here ] WARNING: CPU: 0 PID: 1 at kernel/memremap.c:111 memremap+0x118/0x194 memremap attempted on ram

Re: [PATCH v3 2/2] media: et8ek8: Add documentation

On 15.06.2016 21:41, Rob Herring wrote: On Tue, Jun 14, 2016 at 11:31 PM, Sakari Ailus <sakari.ai...@iki.fi> wrote: Hi Rob, On Tue, Jun 14, 2016 at 05:05:17PM -0500, Rob Herring wrote: On Sat, Jun 11, 2016 at 06:39:53PM +0300, Ivaylo Dimitrov wrote: Add DT bindings descr

[RESEND PATCH v2 5/5] ir-rx51: use hrtimer instead of dmtimer

Drop dmtimer usage for pulse timer in favor of hrtimer. That allows removing PWM dmitimer platform data usage. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/mach-omap2/board-rx51-peripherals.c | 4 - arch/arm/mach-omap2/pdata-quirks.c | 3 - d

[RESEND PATCH v2 3/5] ir-rx51: use PWM framework instead of OMAP dmtimer

Convert driver to use PWM framework instead of calling dmtimer functions directly for PWM timer. Remove paragraph about writing to the Free Software Foundation's mailing address while at it. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/mach-omap2/boar

[RESEND PATCH v2 2/5] pwm: omap-dmtimer: Allow for setting dmtimer clock source

source. Allowing setting the clock source by PWM rather than by timer allows different PWMs to have different ranges by not hard-wiring the clock source to the timer. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> Acked-by: Rob Herring <r...@kernel.org> --- Documentatio

[RESEND PATCH v2 0/5] ir-rx51 driver fixes

is needed so the driver to function correctly, without it PWM refuses to set the needed carrier frequency. Changes compared to v1: - removed [PATCH 5/7] ARM: OMAP: dmtimer: Do not call PM runtime functions when not needed. - DT compatible string changed to "nokia,n900-ir" Ivaylo Dimitrov

[RESEND PATCH v2 1/5] ir-rx51: Fix build after multiarch changes broke it

on the previous patch "ARM: OMAP2+: Add more functions to pwm pdata for ir-rx51". Cc: Mauro Carvalho Chehab <mche...@osg.samsung.com> Cc: Neil Armstrong <narmstr...@baylibre.com> Cc: linux-me...@vger.kernel.org Signed-off-by: Tony Lindgren <t...@atomide.com> Si

[RESEND PATCH v2 4/5] ir-rx51: add DT support to driver

With the upcoming removal of legacy boot, lets add support to one of the last N900 drivers remaining without it. As the driver still uses omap dmtimer, add auxdata as well. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> Acked-by: Rob Herring <r...@kernel.org> --- ..

Re: [RESEND PATCH v2 1/5] ir-rx51: Fix build after multiarch changes broke it

On 23.06.2016 20:48, Pali Rohár wrote: On Wednesday 22 June 2016 21:22:17 Ivaylo Dimitrov wrote: The ir-rx51 driver for n900 has been disabled since the multiarch changes as plat include directory no longer is SoC specific. Let's fix it with minimal changes to pass the dmtimer calls in pdata

[PATCH v1] ARM: RX51: Set system_rev from ATAGS

This fixed a regression with DT boot compared to legacy boot. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/mach-omap2/board-generic.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-omap2/board-generi

Re: [PATCH] ARM: OMAP2+: Fix onenand initialization to avoid filesystem corruption

Hi On 8.02.2016 21:36, Tony Lindgren wrote: OK. So probably the INT or RDY polarity made the ECC not work. Well, ECC disable bit (ONENAND_SYS_CFG1_NO_ECC) was set as well, so most probably it was the bugger :) Aaro, care to dump out also the nolo configured CFG1 value from n8x0 and

[PATCH] ARM: RX51: Set system_rev from ATAGS

Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/mach-omap2/board-generic.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-omap2/board-generic.c b/arch/arm/mach-omap2/board-generic.c index 8098272..b91fabe

[PATCH] ARM: OMAP2+: Fix onenand initialization to avoid filesystem corruption

Commit ("ARM: OMAP2+: Fix onenand rate detection to avoid filesystem corruption") partially fixed onenand configuration when GPMC module is reset. Finish the job by also providing the correct values in ONENAND_REG_SYS_CFG1 register. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov

Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator

Hi Tomi, On 11.01.2016 20:34, Tomi Valkeinen wrote: So, I'm not very enthusiastic about adding this feature as an omapfb specific boot parameter. What about something like (not properly formatted, just want your opinion on the idea): diff --git a/arch/arm/mach-omap2/fb.c

[PATCH] power: bq27xxx_battery: Restore device name

Patch <703df6c097956d17a818e63961c82e8e9eef9fef> ("power: bq27xxx_battery: Reorganize I2C into a module") has removed the device name numbering from bq27xxx_battery_i2c_probe. Fix that by restoring the code. Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com&

[PATCH] ARM: dts: omap3-n900: Allow gpio keys to be disabled

Add linux,can-disable; to all gpios exported from gpio-keys driver, so userspace can disable them Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov...@gmail.com> --- arch/arm/boot/dts/omap3-n900.dts | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/omap3-n900.dts

  1   2   3   4   5   >