On 19.12.24 г. 9:53 ч., Jiri Slaby wrote:
On 19. 12. 24, 8:45, Ivaylo Dimitrov wrote:
Hi,
...
On 29.11.20 г. 22:51 ч., Pavel Machek wrote:
It looks like you may also have a problem with tty hangups, which
serdev
does not support currently. There are multiple paths in n_gsm which can
Hi,
...
On 29.11.20 г. 22:51 ч., Pavel Machek wrote:
It looks like you may also have a problem with tty hangups, which serdev
does not support currently. There are multiple paths in n_gsm which can
trigger a hangup (e.g. based on remote input) and would likely lead to a
crash
I don't believe
Hi,
On 27.11.20 г. 19:30 ч., Tomi Valkeinen wrote:
On 27/11/2020 17:37, Ivaylo Dimitrov wrote:
With 5.9.11 and the patch on top, n900 boots fine, albeit display remains
blank, could be related to
brightness, we're still investigating.
Ok. A DSS regdump for a working version and the l
Hi,
On 27.11.20 г. 15:10 ч., Ivaylo Dimitrov wrote:
On 27.11.20 г. 13:45 ч., Tomi Valkeinen wrote:
On 27/11/2020 01:17, Ivaylo Dimitrov wrote:
Hi Tomi,
On 26.11.20 г. 16:11 ч., Tomi Valkeinen wrote:
Hi Aaro, Ivaylo,
On 24/11/2020 23:03, Ivaylo Dimitrov wrote:
Is there any progress on
On 27.11.20 г. 13:45 ч., Tomi Valkeinen wrote:
On 27/11/2020 01:17, Ivaylo Dimitrov wrote:
Hi Tomi,
On 26.11.20 г. 16:11 ч., Tomi Valkeinen wrote:
Hi Aaro, Ivaylo,
On 24/11/2020 23:03, Ivaylo Dimitrov wrote:
Is there any progress on the issue? I tried 5.9.1 and still nothing displayed
Hi Tomi,
On 26.11.20 г. 16:11 ч., Tomi Valkeinen wrote:
Hi Aaro, Ivaylo,
On 24/11/2020 23:03, Ivaylo Dimitrov wrote:
Is there any progress on the issue? I tried 5.9.1 and still nothing displayed.
Can you test the attached patch?
With this patch I don't see oops that Aaro reporte
Hi,
On 25.08.20 г. 16:16 ч., Tomi Valkeinen wrote:
Hi Laurent,
On 23/08/2020 19:26, Aaro Koskinen wrote:
Hi,
On Tue, Aug 04, 2020 at 03:39:37PM +0300, Tomi Valkeinen wrote:
On 04/08/2020 15:13, Tomi Valkeinen wrote:
Can you try to pinpoint a bit where the hang happens? Maybe add
DRM/omapd
Hi,
On 8.03.2018 15:21, Pali Rohár wrote:
On Thursday 08 March 2018 13:27:15 Pavel Machek wrote:
Hi!
Resent without non-upstream patches.
This backport patchset fixed the spectre issue, it's original branch:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=kpti
A few d
Hi,
On 5.03.2018 19:38, Bin Liu wrote:
On Wed, Feb 28, 2018 at 01:59:43PM -0800, Tony Lindgren wrote:
* Merlijn Wajer [180227 22:29]:
Without pm_runtime_{get,put}_sync calls in place, reading
vbus status via /sys causes the following error:
Unhandled fault: external abort on non-linefetch (
On 3.01.2018 17:40, Pali Rohár wrote:
On Wednesday 03 January 2018 16:34:15 Filip Matijević wrote:
Hi,
On 01/03/2018 02:56 PM, Pavel Machek wrote:
Hi!
Sebasian, you submitted patch to enable vibrations on N950. I am
trying to do the same now on N9... I guess I enabled the dts, but
.. how d
aliases for lcd and tv
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index 669c51c..4b9c3a7 100644
--- a/arch/arm/boot/dts/omap3-n900.dts
Hi,
On 20.12.2017 19:54, Laurent Pinchart wrote:
Hi Pavel,
On Saturday, 4 February 2017 23:56:10 EET Pavel Machek wrote:
Hi!
+Required properties
+===
+
+compatible : must contain "video-bus-switch"
How generic is this? Should we have e.g. nokia,video-bus-switch? And
if
Hi,
On 10.11.2017 22:54, Pavel Machek wrote:
Hi!
Hi! Yesterday I updated https://elinux.org/N900 page based on data which
I found in linux git repository. So driver status should be
up-to-date.
BTW... do you have any reasonable userland to run on n900?
There is devuan jessie N900 image, I
Hi
On 28.08.2017 18:07, Sakari Ailus wrote:
Hi Pavel,
On Mon, Aug 28, 2017 at 03:59:59PM +0200, Pavel Machek wrote:
Hi!
Well, strobe property above already uses = <0>/<1> format, as do
others.
Problem with "false = property does not exist" is that you don't know
if it is "someone forgot t
On 27.04.2017 01:51, Pavel Machek wrote:
Hi!
There are two separate things here:
1) Autofoucs for a device that doesn't use subdev API
2) libv4l2 support for devices that require MC and subdev API
Actually there are three: 0) autogain. Unfortunately, I need autogain
first before autofocus
Hi,
On 26.04.2017 16:23, Pavel Machek wrote:
Hi!
I don't see why it would be hard to open files or have threads inside
a library. There are several libraries that do that already, specially
the ones designed to be used on multimidia apps.
Well, This is what the libv4l2 says:
This file im
Hi
On 16.01.2017 12:10, Sean Young wrote:
Have you had a chance to test the ir-rx51 changes?
Thanks
Sean
Still no, and afaik there are issues booting n900 with current kernel.
Will try to find time over the weekend.
Ivo
On 3.01.2017 13:21, Bastien Nocera wrote:
On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote:
On Monday 02 January 2017 16:27:05 Bastien Nocera wrote:
On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote:
This patch allows user to disable events from any input device so
events
would not be
On 30.12.2016 15:30, Sean Young wrote:
On Fri, Dec 30, 2016 at 01:07:52PM +, Sean Young wrote:
Hi Ivo,,
On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote:
On 20.12.2016 19:50, Sean Young wrote:
This driver was written using lirc since rc-core did not support
transmitter
Hi,
On 20.12.2016 19:50, Sean Young wrote:
This driver was written using lirc since rc-core did not support
transmitter-only hardware at that time. Now that it does, port
this driver.
Compile tested only.
I guess after that change, there will be no more /dev/lircN device,
right? Neither wil
Hi,
On 23.12.2016 13:42, Pavel Machek wrote:
Hi!
[...]
static int isp_subdev_notifier_bound(struct v4l2_async_notifier *async,
diff --git a/drivers/media/platform/video-bus-switch.c
b/drivers/media/platform/video-bus-switch.c
index 1a5d944..3a2d442 100644
--- a/drivers/media/platform/video-
Hi
On 14.12.2016 15:03, Pali Rohár wrote:
Hi! See inlined some my notes.
+
+#ifdef USE_CRC
+ rval = et8ek8_i2c_read_reg(client, ET8EK8_REG_8BIT, 0x1263, &val);
+ if (rval)
+ goto out;
+#if USE_CRC /* TODO get crc setting from DT */
+ val |= BIT(4);
+#else
+
Hi,
On 24.11.2016 17:20, Pali Rohár wrote:
In case when wl1251 is statically linked into kernel image, it is loaded
and initialized before even userspace applications starts.
Which leaves no option, but integrating libcal into kernel :).
Ivo
Hi,
On 4.11.2016 01:05, Sakari Ailus wrote:
Hi Sebastian,
On Thu, Nov 03, 2016 at 11:48:43PM +0100, Sebastian Reichel wrote:
Hi,
On Tue, Nov 01, 2016 at 12:54:08AM +0200, Sakari Ailus wrote:
Thanks, this answered half of my questions already. ;-)
:-).
I'll have to go through the patches,
On 2.11.2016 10:15, Pavel Machek wrote:
Hi!
I'll have to go through the patches, et8ek8 driver is probably not
enough to get useful video. platform/video-bus-switch.c is needed for
camera switching, then some omap3isp patches to bind flash and
autofocus into the subdevice.
Then, device tree
On 1.11.2016 22:11, Sakari Ailus wrote:
Hi Ivaylo,
On Tue, Nov 01, 2016 at 08:36:57AM +0200, Ivaylo Dimitrov wrote:
Hi,
On 1.11.2016 00:54, Sakari Ailus wrote:
Hi Pavel,
On Sun, Oct 23, 2016 at 10:33:15PM +0200, Pavel Machek wrote:
Hi!
Thanks, this answered half of my questions
Hi,
On 1.11.2016 00:54, Sakari Ailus wrote:
Hi Pavel,
On Sun, Oct 23, 2016 at 10:33:15PM +0200, Pavel Machek wrote:
Hi!
Thanks, this answered half of my questions already. ;-)
:-).
I'll have to go through the patches, et8ek8 driver is probably not
enough to get useful video. platform/vid
changed according to the comments on v1
Ivaylo Dimitrov (2):
media: Driver for Toshiba et8ek8 5MP sensor
media: et8ek8: Add documentation
Is there any progress here? Is there any way I could help?
There were some notes I need to address, unfortunately no spare time lately
:( . Feel free to
- code changed according to the comments on v1
Ivaylo Dimitrov (2):
media: Driver for Toshiba et8ek8 5MP sensor
media: et8ek8: Add documentation
Is there any progress here? Is there any way I could help?
There were some notes I need to address, unfortunately no spare time
lately :( . Feel
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
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
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 1 -
arch/arm
pends on the previous patch
"ARM: OMAP2+: Add more functions to pwm pdata for ir-rx51".
Cc: Mauro Carvalho Chehab
Cc: Neil Armstrong
Cc: linux-me...@vger.kernel.org
Signed-off-by: Tony Lindgren
Signed-off-by: Ivaylo Dimitrov
Acked-by: Pavel Machek
---
drivers/media/rc/Kconfig |
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
Acked-by: Rob Herring
---
.../devicetree/bindings/media/nokia,n900-ir | 20
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
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pwm/pwm-omap-dmtimer.txt | 4
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
Drop dmtimer usage for pulse timer in favor of hrtimer. That allows
removing PWM dmitimer platform data usage.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 4 -
arch/arm/mach-omap2/pdata-quirks.c | 3 -
drivers/media/rc/ir-rx51.c
On 15.06.2016 21:41, Rob Herring wrote:
On Tue, Jun 14, 2016 at 11:31 PM, Sakari Ailus 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 description
Not exactly the best commit msg
Hi,
On 13.06.2016 10:10, Tony Lindgren wrote:
* Ivaylo Dimitrov [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 driver maintainers to
apply.
Alread
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
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
---
Hi Pavel,
I also don't think the FOCUS_ABSOLU
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
Add DT bindings description
Signed-off-by: Ivaylo Dimitrov
---
.../bindings/media/i2c/toshiba,et8ek8.txt | 50 ++
1 file changed, 50 insertions(+)
create mode 100644
Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.txt
diff --git a/Documentation
The sensor is found in Nokia N900 main camera
Signed-off-by: Ivaylo Dimitrov
---
drivers/media/i2c/Kconfig|1 +
drivers/media/i2c/Makefile |1 +
drivers/media/i2c/et8ek8/Kconfig |6 +
drivers/media/i2c/et8ek8/Makefile|2 +
drivers
The sensor is found in Nokia N900 main camera
Signed-off-by: Ivaylo Dimitrov
---
drivers/media/i2c/Kconfig|1 +
drivers/media/i2c/Makefile |1 +
drivers/media/i2c/et8ek8/Kconfig |6 +
drivers/media/i2c/et8ek8/Makefile|2 +
drivers
Add DT bindings description
Signed-off-by: Ivaylo Dimitrov
---
.../bindings/media/i2c/toshiba,et8ek8.txt | 50 ++
1 file changed, 50 insertions(+)
create mode 100644
Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.txt
diff --git a/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
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
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
+++ b/include/uapi/linux/v4l2-co
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
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 m
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 0x8f
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()
function
On 24.05.2016 12:04, Pavel Machek wrote:
Hi!
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+ struct ad5820_device *coil = to_ad5820_device(subdev);
+ struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+ coil->vana = regulator_get(&client->dev, "VANA");
Hi,
On 21.05.2016 13:56, Pavel Machek wrote:
This adds support for AD5820 autofocus coil, found for example in
Nokia N900 smartphone.
Signed-off-by: Pavel Machek
---
v2: simple cleanups, fix error paths, simplify probe
v3: more cleanups, remove printk, add include
diff --git a/drivers/media
Hi,
On 21.05.2016 08:43, Pavel Machek wrote:
This adds support for AD5820 autofocus coil, found for example in
Nokia N900 smartphone.
Signed-off-by: Pavel Machek
---
v2: simple cleanups, fix error paths, simplify probe
I think it is ready. Please apply :-).
diff --git a/drivers/media/i2c/Kc
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
---
.../devicetree/bindings/media/nokia,n900-ir | 20
arch
From: Tony Lindgren
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. Then the following changes can be done while things can
be tested to be working
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
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
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 1 -
arch/arm
Add the needed DT data to enable IR TX driver
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index b3c26a9..cb3878a 100644
--- a/arch/arm
Drop dmtimer usage for pulse timer in favor of hrtimer. That allows
removing PWM dmitimer platform data usage.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 4 -
arch/arm/mach-omap2/pdata-quirks.c | 3 -
drivers/media/rc/ir-rx51.c
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
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pwm/pwm-omap-dmtimer.txt | 4
Hi,
On 11.05.2016 17:14, Rob Herring wrote:
On Tue, May 10, 2016 at 04:18:27AM +0200, Sebastian Reichel wrote:
Hi,
On Mon, May 09, 2016 at 04:07:35PM -0500, Rob Herring wrote:
There's already a pwm-led binding that can be used. Though there
may be missing consumer IR to LED subsystem support
On 10.05.2016 00:07, Rob Herring wrote:
On Mon, May 9, 2016 at 3:53 PM, Ivaylo Dimitrov
wrote:
Hi,
On 9.05.2016 23:06, Rob Herring wrote:
On Sat, May 07, 2016 at 06:21:45PM +0300, Ivaylo Dimitrov wrote:
With the upcoming removal of legacy boot, lets add support to one of the
last N900
Hi,
On 9.05.2016 23:06, Rob Herring wrote:
On Sat, May 07, 2016 at 06:21:45PM +0300, Ivaylo Dimitrov wrote:
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
Hi,
On 9.05.2016 22:36, Tony Lindgren wrote:
* Ivaylo Dimitrov [160507 08:24]:
once omap_dm_timer_start() is called, which calls omap_dm_timer_enable()
and thus pm_runtime_get_sync(), it doesn't make sense to call PM runtime
functions again before omap_dm_timer_stop is called(). Otherwi
From: Tony Lindgren
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. Then the following changes can be done while things can
be tested to be working
eeded
delays.
Fix that by implementing an "enabled" counter, so the PM runtime functions
get called only when really needed.
Without that patch Nokia N900 IR TX driver (ir-rx51) does not function.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/plat-omap/dmtimer.c | 9 -
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
---
Documentation/devicetree/bindings/pwm/pwm-omap-dmtimer.txt | 4
drivers/pwm/pwm-omap
Drop dmtimer usage for pulse timer in favor of hrtimer. That allows
removing PWM dmitimer platform data usage.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 4 -
arch/arm/mach-omap2/pdata-quirks.c | 3 -
drivers/media/rc/ir-rx51.c
Add the needed DT data to enable IR TX driver
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index b3c26a9..3d1e23e 100644
--- a/arch/arm
are needed so the driver to function correctly, without
those PWM either refuses to set the needed carrier frequency (patch 2)
or there are such a delays in the PWM framework, code that transmission
duration raises to ~5s instead of half a second.
Ivaylo Dimitrov (6):
pwm: omap-dmtimer: Allow for
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
---
.../devicetree/bindings/media/nokia,lirc-rx51 | 19 +++
arch
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
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 1 -
arch/arm
Hi,
On 2.05.2016 10:06, Pavel Machek wrote:
On Fri 2016-04-22 15:49:29, Pali Rohár wrote:
On Tuesday 05 January 2016 17:12:50 Tony Lindgren wrote:
* Pali Rohár [160105 02:19]:
On Saturday 02 January 2016 09:06:57 Tony Lindgren wrote:
Yup please take a look at thread "[PATCH 0/3] pwm: omap
Hi,
On 30.04.2016 01:20, Pali Rohár wrote:
On Saturday 30 April 2016 00:13:59 Pavel Machek wrote:
Any other application I should look at? Thanks,
Maybe camera-ui, which is part of CSSU?
https://github.com/community-ssu/camera-ui
This is based on gdigicam, are you sure it is compatible wit
are no known problems caused by that, it is
better to follow what TRM says.
Signed-off-by: Ivaylo Dimitrov
---
drivers/regulator/twl-regulator.c | 78 +++
1 file changed, 70 insertions(+), 8 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b
Hi,
On 24.04.2016 19:11, Pavel Machek wrote:
On Sat 2016-03-26 10:28:15, Ivaylo Dimitrov wrote:
When machine constraints are applied, regulator framework first sets
initial mode (if any) and then enables the regulator if needed. The current
code in twl4030reg_set_mode always checks if the
On 16.04.2016 09:20, Ivaylo Dimitrov wrote:
According to the TRM, SCM CONTROL_CSIRXFE register is on offset 0x6c
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap34xx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch
Hi,
On 18.04.2016 00:44, Sakari Ailus wrote:
Hi Ivaylo,
On Sat, Apr 16, 2016 at 11:12:20AM +0300, Ivaylo Dimitrov wrote:
Some sensors (like the one in Nokia N900) provide metadata in the first
couple of lines. Make that information information available to the
pipeline.
Signed-off-by: Ivaylo
Without that, regulators are left in the mode last set by the bootloader or
by the kernel the device was rebooted from. This leads to various problems,
like non-working peripherals.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 9 +
1 file changed, 9 insertions
On 17.04.2016 03:05, Sebastian Reichel wrote:
Hi Ivo,
On Sat, Apr 16, 2016 at 09:37:23AM +0300, Ivaylo Dimitrov wrote:
Without that, regulators are left in the mode last set by the bootloader or
by the kernel the device was rebooted from. This leads to various problems
like non-working
Some sensors (like the one in Nokia N900) provide metadata in the first
couple of lines. Make that information information available to the
pipeline.
Signed-off-by: Ivaylo Dimitrov
---
drivers/media/i2c/smiapp/smiapp-core.c | 12
drivers/media/i2c/smiapp/smiapp.h | 1 +
2
Without that, regulators are left in the mode last set by the bootloader or
by the kernel the device was rebooted from. This leads to various problems
like non-working peripherals.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 9 +
1 file changed, 9 insertions
According to the TRM, SCM CONTROL_CSIRXFE register is on offset 0x6c
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap34xx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi
index 5cdba1f..e446562
Hi,
On 7.04.2016 17:46, Ivaylo Dimitrov wrote:
Hi,
On 7.04.2016 17:25, Alan Stern wrote:
On Thu, 7 Apr 2016, Michal Nazarewicz wrote:
Sounds good to me. I’d love someone to test this patch (I sadly have no
way of doing that at the moment) and with that I can resend it with
updated
Hi,
On 7.04.2016 17:25, Alan Stern wrote:
On Thu, 7 Apr 2016, Michal Nazarewicz wrote:
Sounds good to me. I’d love someone to test this patch (I sadly have no
way of doing that at the moment) and with that I can resend it with
updated message.
Ivaylo should be able to try it.
I applied
which
results in writing to a wrong register. Fix that by providing the correct
register value.
Signed-off-by: Ivaylo Dimitrov
---
drivers/regulator/twl-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator
On 26.03.2016 10:28, Ivaylo Dimitrov wrote:
According to the TRM, we need to enable i2c access to powerbus before
writing to it. Also, a new write to powerbus should not be attempted if
there is a pending transfer. The current code does not implement that
functionality and while there are no
of_map_mode is needed so to be possible to set initial regulators mode from
the board DTS. Otherwise, for DT boot, regulators are left in their default
state after reset/reboot. Document device specific modes as well.
Signed-off-by: Ivaylo Dimitrov
---
.../bindings/regulator/twl-regulator.txt
of_map_mode is needed so to be possible to set initial regulators mode from
the board DTS. Otherwise, for DT boot, regulators are left in their default
state after reset/reboot. Document device specific modes as well.
Signed-off-by: Ivaylo Dimitrov
---
.../devicetree/bindings/regulator/twl
of_map_mode is needed so to be possible to set initial regulators mode from
the board DTS. Otherwise, for DT boot, regulators are left in their default
state after reset/reboot.
Signed-off-by: Ivaylo Dimitrov
---
drivers/regulator/twl-regulator.c | 16 +---
1 file changed, 13
follow what TRM says.
Signed-off-by: Ivaylo Dimitrov
---
drivers/regulator/twl-regulator.c | 78 +++
1 file changed, 70 insertions(+), 8 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator.c
index 955a6fb..aad748b0
ys-on" regulators which have "initial-mode" set in the board DTS. Fix
that by removing the unneeded check.
Signed-off-by: Ivaylo Dimitrov
---
drivers/regulator/twl-regulator.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regul
nality for initial mode setting
from the board DTS. Fix i2c access to powerbus while at it.
I will send a follow-up patch for N900 board DTS that sets initial
regulators mode once the $subject series is assumed to be ok.
Ivaylo Dimitrov (3):
regulator: twl: Make sure we have access to powerbus bef
On 26.03.2016 00:28, Mark Brown wrote:
On Fri, Mar 25, 2016 at 09:19:12PM +0100, Sebastian Reichel wrote:
On Fri, Mar 25, 2016 at 06:20:17PM +, Mark Brown wrote:
Then there is a constraint that the regulators must be in normal mode
and this needs to be expressed in the machine constrain
On 25.03.2016 19:05, Mark Brown wrote:
On Fri, Mar 25, 2016 at 06:50:18PM +0200, Ivaylo Dimitrov wrote:
On 25.03.2016 18:19, Mark Brown wrote:
What makes you claim that this is a bug in the framework? Does anything
in the machine configuration say that changing the modes is allowed?
My
On 25.03.2016 18:19, Mark Brown wrote:
On Fri, Mar 25, 2016 at 06:09:27PM +0200, Ivaylo Dimitrov wrote:
Ok, so you say that regulator framework should call twl4030reg_set_mode(),
but it doesn't. If that is the case, then the bug is in the regulator
framework, a similar one to what y
On 25.03.2016 17:54, Mark Brown wrote:
On Fri, Mar 25, 2016 at 04:02:59PM +0100, Sebastian Reichel wrote:
On Fri, Mar 25, 2016 at 11:17:57AM +, Mark Brown wrote:
On Wed, Mar 23, 2016 at 09:22:36PM +0200, Ivaylo Dimitrov wrote:
Assigning a device group to a regulator does not change
: Ivaylo Dimitrov
---
drivers/regulator/twl-regulator.c | 85 ++-
1 file changed, 75 insertions(+), 10 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator.c
index 955a6fb..125d5b1 100644
--- a/drivers/regulator/twl
1 - 100 of 205 matches
Mail list logo
