Re: [Gta04-owner] [PATCH 10/13] twl4030_charger: add software controlled linear charging mode.

cal characteristics of a bicycle as a power source are. - the amount of current available changes - 500mA at around 17km/h - you cannot destroy it by electrically overloading If the current is set to e.g. 500mA and that linear charging mode is enabled, the battery gets the maximum current available (upto 500mA) regardless of the speed which is often changing. Regards, Andreas Kemnade signature.asc Description: PGP signature

[PATCH] omap_hdq: fix usecount handling

hdq_usecount was set to zero after a successful read, so omap_hdq_put could not properly free resources which leads e.g. to increasing usecounts in lsmod output Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/w1/masters/omap_hdq.c | 1 - 1 file changed, 1 deletion(-)

[PATCH 1/6] wireless:libertas: do not strip header for PS_MODE commands

struct cmd_ds_802_11_ps_mode contains the command header and a pointer to it was initialized with data points to the body which leads to mis-interpretation of the cmd_ds_802_11_ps_mode.action member. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/net/wireless/libertas

[PATCH 2/6] wireless:libertas: check whether bus can do more than polling

If a sdio host does not support sdio irqs, polling is used instead. That has an impact on performance. Some functionality should not be enabled then. This add a variable in libertas_priv to indicate that. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/net/wireless/li

[PATCH 0/6] wireless:libertas: ieee80211 powersave mode

This series makes IEEE 80211 powersave mode work again so that power usage is dramatically reduced when the device is connected. It does not include other power saving methods which are working when the device is not connected (like enabling deep sleep modus) Tested on GTA04 which includes a

[PATCH 4/6] wireless:libertas: do not confirm sleep if commands are pending

If the main thread gets one PS AWAKE event and one PS SLEEP event in one iteration over event_fifo there will never be checks for commands to be processed, since psstate will always be PS_STATE_SLEEP or PS_STATE_PRE_SLEEP Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drive

[PATCH 3/6] wireless:libertas: add an cfg80211 interface for powersaving

such conditions. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/net/wireless/libertas/cfg.c | 38 + 1 file changed, 38 insertions(+) diff --git a/drivers/net/wireless/libertas/cfg.c b/drivers/net/wireless/libertas/cfg.c index 8317afd..f

[PATCH 6/6] wireless:libertas: fix suspend problems

When the device goes to suspend mode with powersaving enabled, lbs_remove_card tries to exit powersaving state even when already woken up. That command is not processed properly in that situation, so the system hangs at suspend, so disable it. Signed-off-by: Andreas Kemnade <andr...@kemnade.i

[PATCH 5/6] wireless:libertas: go back to ps mode without commands pending

is needed. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/net/wireless/libertas/cmd.c | 36 +--- 1 file changed, 5 insertions(+), 31 deletions(-) diff --git a/drivers/net/wireless/libertas/cmd.c b/drivers/net/wireless/libertas/cmd.c index 4

[PATCH] net/wireless/libertas: do not strip header for PS_MODE commands

struct cmd_ds_802_11_ps_mode contains the command header and a pointer to it was initialized with data points to the body which leads to mis-interpretation of the cmd_ds_802_11_ps_mode.action member. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/net/wireless/libertas

Re: [Gta04-owner] [PATCH 10/13] twl4030_charger: add software controlled linear charging mode.

CC/CV mode is still automatically done, but end of charge due to low current not. Note: If linear charging mode is used there should be some method of stopping charging automatically. It is not a so time-critical, but it is the wrong setting fo

Re: [PATCH RESEND] omap_hdq: fix usecount handling

ping... On Tue, 19 Jan 2016 10:13:04 -0800 "gre...@linuxfoundation.org" wrote: > On Tue, Jan 19, 2016 at 07:38:28PM +0300, Evgeniy Polyakov wrote: > > Hi Andreas > > > > >From w1 perspective this doesn't break things :) > > Greg, please pull it into your tree if no

[PATCH v3 4/6] libertas: go back to ps mode without commands pending

is needed. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes in v3: corrected paths changes in v2: reordered, was 5/6 drivers/net/wireless/marvell/libertas/cmd.c | 36 +--- 1 file changed, 5 insertions(+), 31 deletions(-) diff --git a/drive

[PATCH v3 1/6] libertas: fix pointer bugs for PS_MODE commands

and buffer This piece of code was unused since power saving was not enabled. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes in v3: corrected paths changes in v2: improved commit message drivers/net/wireless/marvell/libertas/cmd.c | 4 ++-- drivers/net/wireless/marvell

[PATCH v3 2/6] libertas: check whether bus can do more than polling

If a sdio host does not support sdio irqs, polling is used instead. That has an impact on performance. Some functionality should not be enabled then. This add a variable in libertas_priv to indicate that. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes in v3: corrected

[PATCH v3 0/6] libertas: ieee80211 powersave mode

This series makes IEEE 80211 powersave mode work again so that power usage is dramatically reduced when the device is connected. It does not include other power saving methods which are working when the device is not connected (like enabling deep sleep modus) Tested on GTA04 which includes a

[PATCH v3 6/6] libertas: add an cfg80211 interface for powersaving

such conditions. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes in v3: corrected paths changes in v2: reordered, was 3/6 drivers/net/wireless/marvell/libertas/cfg.c | 38 + 1 file changed, 38 insertions(+) diff --git a/drivers/net/wireless/m

[PATCH v3 3/6] libertas: do not confirm sleep if commands are pending

If the main thread gets one PS AWAKE event and one PS SLEEP event in one iteration over event_fifo there will never be checks for commands to be processed, since psstate will always be PS_STATE_SLEEP or PS_STATE_PRE_SLEEP Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes

[PATCH v3 5/6] libertas: fix ps-mode related removal problems

forever for the command being processed, so disable it. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes in v3: corrected paths changes in v2: improved commit message, reordered: was 6/6 drivers/net/wireless/marvell/libertas/main.c | 7 ++- 1 file changed, 6 insertions

Re: [Gta04-owner] [PATCH 0/4] UART slave device support - version 4

On Fri, 22 Jan 2016 20:12:29 + One Thousand Gnomes wrote: > > I would have expected that the main (and IMO sufficient) reason why > > the kernel should do it is because the particular bus used to connect > > a BT chip to the CPU is a hw detail that a kernel that

Re: [PATCH RFC] wireless:libertas: enable auto deep sleep

On Wed, 20 Jan 2016 14:42:47 +0200 Kalle Valo <kv...@codeaurora.org> wrote: > Andreas Kemnade <andr...@kemnade.info> writes: > > > Enables auto deep sleep whenever the interface is up and > > power managament is enabled, so there is also power management &

Re: [PATCH] musb: omap2430: do not assume balanced enable()/disable()

On Tue, 2 Aug 2016 03:33:34 -0700 Tony Lindgren <t...@atomide.com> wrote: > * Andreas Kemnade <andr...@kemnade.info> [160729 11:14]: > > The code assumes that omap2430_musb_enable() and > > omap2430_musb_disable() is called in a balanced way. The > >

Re: [PATCH] musb: omap2430: do not assume balanced enable()/disable()

On Tue, 2 Aug 2016 23:30:16 -0700 Tony Lindgren <t...@atomide.com> wrote: > * Andreas Kemnade <andr...@kemnade.info> [160802 08:14]: > > On Tue, 2 Aug 2016 03:33:34 -0700 > > Tony Lindgren <t...@atomide.com> wrote: > > > > > * Andr

[PATCH v2] musb: omap2430: do not assume balanced enable()/disable()

events phy_power_off() from being called when it is already off. Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- changes in v2: improved commit message drivers/usb/musb/omap2430.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/usb/musb/omap2430

Re: [Letux-kernel] [PATCH v2] musb: omap2430: do not assume balanced enable()/disable()

Hi, On Thu, 4 Aug 2016 07:29:19 -0700 Tony Lindgren wrote: > Hi, > > * H. Nikolaus Schaller [160803 10:07]: > > All this prevents detection of cable plugin-events and VBUS > > measurement and setting OTG_EN before charging is attempted. > > So I gave

Re: [Letux-kernel] [PATCH v2] musb: omap2430: do not assume balanced enable()/disable()

On Thu, 4 Aug 2016 16:49:30 +0200 "H. Nikolaus Schaller" wrote: > > Rationale: > > > > The charger driver calls pm_runtime_get_sync(bci->transceiver->dev); > > which should indirectly call twl4030_usb_set_mode to set the > > POWER_CTRL_OTG_ENAB bit. This enables the

Re: [Letux-kernel] [PATCH v2] musb: omap2430: do not assume balanced enable()/disable()

On Fri, 5 Aug 2016 23:21:35 -0700 Tony Lindgren <t...@atomide.com> wrote: > * Andreas Kemnade <andr...@kemnade.info> [160805 08:35]: > > I repeat the subject line of the patch: > > [PATCH v2] musb: omap2430: do not assume balanced enable()/disable() > > It is *n

[PATCH] musb: omap2430: do not assume balanced enable()/disable()

off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/usb/musb/omap2430.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c index aecb934..c7ae117 100644 --- a/drivers/usb/musb/omap2430.c +++ b/drivers

Re: [Letux-kernel] [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi Dmitry, On Fri, 17 Feb 2017 12:40:41 -0800 Dmitry Torokhov wrote: [...] > > Let me cite myself: > > > > >> This makes it possible to pre-calibrate the touch so that is > > >> (almost) > > Yes, it allows you to pre-calibrate, I get it. But you still do > properly

Re: [Letux-kernel] [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, On Sun, 19 Feb 2017 21:57:08 +0100 Pavel Machek wrote: > Hi! > > > > But as said I don't think we need float or fixed point for > > practical systems at all. > > So you are going to loose precision. And if userspace decides to > calibrate it slightly differently from

Re: [Letux-kernel] [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, [...] > > Hm. Why not touching pixel (0,0) on the touch is always pixel (0,0) > > on the screen and touching pixel (639,479) is always (639,479)? > > Important is that there is no 1:1 mapping between input evdev device > and drm/fb output device. These are two independent devices. There is >

Re: [Letux-kernel] [PATCH v2] musb: omap2430: do not assume balanced enable()/disable()

On Thu, 4 Aug 2016 18:31:29 +0200 Andreas Kemnade <andr...@kemnade.info> wrote: > Hi, > > On Thu, 4 Aug 2016 07:29:19 -0700 > Tony Lindgren <t...@atomide.com> wrote: > > > Hi, > > > > * H. Nikolaus Schaller <h...@goldelico.com> [160803 10:07]

Re: [Letux-kernel] [PATCH v2] musb: omap2430: do not assume balanced enable()/disable()

On Fri, 5 Aug 2016 06:55:01 -0700 Tony Lindgren <t...@atomide.com> wrote: > * Andreas Kemnade <andr...@kemnade.info> [160804 09:44]: > > Nothing happens here, so the previous state of the phy remains. > > It would be disabled by the generic phy layer in > > driver

Re: [v2] musb: omap2430: do not assume balanced enable()/disable()

On Fri, 9 Sep 2016 16:40:15 -0700 Tony Lindgren <t...@atomide.com> wrote: > * Tony Lindgren <t...@atomide.com> [160909 14:33]: > > * Andreas Kemnade <andr...@kemnade.info> [160909 14:22]: > > > We have two independant things: > > > 1. phy-t

Re: [v2] musb: omap2430: do not assume balanced enable()/disable()

On Fri, 09 Sep 2016 23:21:50 +0300 Laurent Pinchart <laurent.pinch...@ideasonboard.com> wrote: > Hi Tony, > > On Friday 09 Sep 2016 13:08:03 Tony Lindgren wrote: > > * Laurent Pinchart <laurent.pinch...@ideasonboard.com> [160909 > > 12:27]: > > > On Wedn

Re: [v2] musb: omap2430: do not assume balanced enable()/disable()

le() musb_platform_disable() to be called in an unbalanced way by fixing musb_core.c Fixing 1. is enough on gta04 to fix charging and hide 2. enough to have gadget working for the most common usecases. (not using twl4030-charger would not work yet) But in the longer term 2. has to be fixed too. Regards, Andreas Kemnade

[PATCH 1/3] [media] si2157: get chip id during probing

is a symptome of that problem: si2157 7-0063: unknown chip version Si21255-\x\x\x Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/media/tuners/si2157.c | 54 ++ drivers/media/tuners/si2157_priv.h | 7 + 2

[PATCH 0/3] support for Logilink VG0022a DVB-T2 stick

Hi all, here are some patches needed for supporting the Logilink VG0022A DVB-T2 stick. As the combination of chips in that stick is not uncommon, the first two patches might also fix problems for similar hardware. Andreas Kemnade (3): [media] si2157: get chip id during probing [media] af9035

[PATCH 3/3] [media] af9035: add Logilink vg0022a to device id table

Ths adds the logilink VG00022a dvb-t dongle to the device table. The dongle contains (checked by removing the case) IT9303 SI2168 214730 Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/media/usb/dvb-usb-v2/af9035.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/d

[PATCH 2/3] [media] af9035: init i2c already in it930x_frontend_attach

i2c bus is already needed when the frontend is probed, so init it already in it930x_frontend_attach That prevents errors like si2168: probe of 6-0067 failed with error -5 Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/media/usb/dvb-usb-v2/af9035.

Re: [PATCH 0/3] support for Logilink VG0022a DVB-T2 stick

ping On Wed, 15 Mar 2017 23:22:07 +0100 Andreas Kemnade <andr...@kemnade.info> wrote: > Hi all, > here are some patches needed for supporting the > Logilink VG0022A DVB-T2 stick. > As the combination of chips in that stick is not > uncommon, the first two patches mi

Re: [PATCH 1/3] [media] si2157: get chip id during probing

On Sun, 23 Apr 2017 15:19:21 +0300 Antti Palosaari <cr...@iki.fi> wrote: > On 03/16/2017 12:22 AM, Andreas Kemnade wrote: > > If the si2157 is behind a e.g. si2168, the si2157 will > > at least in some situations not be readable after the si268 > > got the command 0101

[PATCH] net: hso: register netdev later to avoid a race condition

e3822080 e1822781 e5981014 (e5832030) [ 1514.510833] ---[ end trace dfb3e53c657f34a0 ]--- Reported-by: H. Nikolaus Schaller <h...@goldelico.com> Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drivers/net/usb/hso.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-)

Re: [PATCH] ARM: Fix __show_regs output timestamps

[ 102.669036] PC is at hso_start_net_device+0x50/0xc0 [hso] [ 102.674835] LR is at hso_net_open+0x68/0x84 [hso] [ 102.679809] pc : []lr : []psr: a00b0013 [ 102.686462] sp : ed047e20 ip : fp : ffff yes, the kernel oopses in a nicer way. Tested-by: Andreas Kemnade <andr

[PATCH] net: hso: fix module unloading

[] (SyS_delete_module+0x160/0x1dc) [40265.985443] [] (SyS_delete_module) from [] (ret_fast_syscall+0x0/0x1c) [40265.994171] Code: c1458d54 e59f3020 e92d4010 e1a04000 (e5941034) [40266.016693] ---[ end trace 9d5ac43c7e41075c ]--- Signed-off-by: Andreas Kemnade <andr...@kemnade.info> --- drive

Re: [PATCH] net: hso: register netdev later to avoid a race condition

On Thu, 27 Apr 2017 10:44:01 +0200 Johan Hovold <jo...@kernel.org> wrote: > On Wed, Apr 26, 2017 at 07:26:40PM +0200, Andreas Kemnade wrote: > > If the netdev is accessed before the urbs are initialized, > > there will be NULL pointer dereferences. That is avoided by &g

Re: [PATCH 1/3] [media] si2157: get chip id during probing

Hi, On Sun, 23 Apr 2017 15:19:21 +0300 Antti Palosaari <cr...@iki.fi> wrote: > On 03/16/2017 12:22 AM, Andreas Kemnade wrote: > > If the si2157 is behind a e.g. si2168, the si2157 will > > at least in some situations not be readable after the si268 > > got the com

Re: [PATCH 2/3] [media] af9035: init i2c already in it930x_frontend_attach

On Wed, 15 Mar 2017 23:22:09 +0100 Andreas Kemnade <andr...@kemnade.info> wrote: > i2c bus is already needed when the frontend is probed, > so init it already in it930x_frontend_attach > That prevents errors like > si2168: probe of 6-0067 failed with error -5 > >

Re: [PATCH 4/7] dt-bindings: gnss: add u-blox binding

On Thu, 3 May 2018 11:35:21 +0200 H. Nikolaus Schaller wrote: > I have realized that the w2sg0004 is an exception (although a Sirf chip) > that it does not provide a WAKEUP signal. And another significant > difference is that we have to keep the serdev UART enabled even if

Re: [Letux-kernel] [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

On Fri, 22 Dec 2017 13:44:27 +0100 Johan Hovold wrote: [...] > I'd suggest reiterating the problem you're trying to solve and > enumerating the previously discussed potential solutions in order to > find a proper abstraction level for this (before getting lost in >

Re: [Letux-kernel] [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

On Fri, 12 Jan 2018 15:46:47 +0100 Johan Hovold <jo...@kernel.org> wrote: > On Tue, Jan 09, 2018 at 06:43:47PM +0100, Andreas Kemnade wrote: > > On Fri, 22 Dec 2017 13:44:27 +0100 > > Johan Hovold <jo...@kernel.org> wrote: > > > > [...] > > > I

[PATCH] usb: musb: fix enumeration after resume

stuff which needs to be enabled. Also interrupts are enabled, as it was the original idea of calling musb_start() in musb_resume() according to Commit 6fc6f4b87cb3 ("usb: musb: Disable interrupts on suspend, enable them on resume") Signed-off-by: Andreas Kemnade <andr...@kemnade.info>

Re: [PATCH] usb: musb: fix enumeration after resume

Hi, On Tue, 6 Feb 2018 12:46:05 -0600 Bin Liu <b-...@ti.com> wrote: > Hi, > > On Sat, Jan 27, 2018 at 09:34:03AM +0100, Andreas Kemnade wrote: > > On dm3730 there are enumeration problems after resume. > > Investigation led to the cause that the MUSB_POWER_

Re: [PATCH] usb: musb: fix enumeration after resume

Hi, On Tue, 6 Feb 2018 10:47:25 -0800 Tony Lindgren <t...@atomide.com> wrote: > * Andreas Kemnade <andr...@kemnade.info> [180127 08:34]: > > On dm3730 there are enumeration problems after resume. > > Investigation led to the cause that the MUSB_POWER_SOFTCONN > &

Re: [PATCH] usb: musb: fix enumeration after resume

On Wed, 7 Feb 2018 14:37:00 -0600 Bin Liu <b-...@ti.com> wrote: > On Tue, Feb 06, 2018 at 08:00:24PM +0100, Andreas Kemnade wrote: > > Hi, > > > > On Tue, 6 Feb 2018 12:46:05 -0600 > > Bin Liu <b-...@ti.com> wrote: > > > > > Hi, > >

[PATCH] pwm: pwm-omap-dmtimer: fix probing problems by returning EPROBE_DEFER

defer probing Fixes: b7290cf6ff78 (pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops) Signed-off-by: Andreas Kemnade --- drivers/pwm/pwm-omap-dmtimer.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/pwm/pwm-omap-dmtimer.c b/drivers/pwm/pwm-omap

Re: bloated defconfigs

Hi, On Sat, 28 Jul 2018 16:01:41 +0300 Andy Shevchenko wrote: > On Sat, Jul 28, 2018 at 3:59 PM, Andreas Kemnade wrote: > > Hi, > > > > I just stumbled upon our defconfigs. > > > > andi@aktux:~/gta04/gta04-kernel$ ls -l arch/arm/configs/ -Sr | tail -n > &g

bloated defconfigs

Hi, I just stumbled upon our defconfigs. andi@aktux:~/gta04/gta04-kernel$ ls -l arch/arm/configs/ -Sr | tail -n 10 -rw-r--r-- 1 andi andi 9524 Apr 7 14:53 imote2_defconfig -rw-r--r-- 1 andi andi 9985 Jul 28 13:34 imx_v6_v7_defconfig -rw-r--r-- 1 andi andi 10118 Apr 7 14:53 ezx_defconfig

[PATCH] phy: phy-twl4030-usb: fix denied runtime access

suspend by plugging in usb. Signed-off-by: Andreas Kemnade --- drivers/phy/ti/phy-twl4030-usb.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/phy/ti/phy-twl4030-usb.c b/drivers/phy/ti/phy-twl4030-usb.c index a44680d64f9b..1f3cf4e48383 100644 --- a/drivers/phy/ti/phy-twl4030

Re: [Letux-kernel] [PATCH 09/32] ARM: dts: omap3-gta04: make NAND partitions compatible with recent U-Boot

On Wed, 25 Jul 2018 10:33:05 +0200 Ladislav Michl wrote: > On Wed, Jul 25, 2018 at 10:18:28AM +0200, H. Nikolaus Schaller wrote: > > > > > Am 25.07.2018 um 10:07 schrieb Ladislav Michl : > > > > > > On Wed, Jul 25, 2018 at 08:58:41AM +0200, H. Nikolaus Schaller wrote: > > >> Vendor defined

[PATCH] mmc: omap_hsmmc: fix wakeirq handling on removal

at removal. Signed-off-by: Andreas Kemnade Fixes: 5b83b2234be6 ("mmc: omap_hsmmc: Change wake-up interrupt to use generic wakeirq") --- drivers/mmc/host/omap_hsmmc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsm

Re: [PATCH] mmc: omap_hsmmc: fix wakeirq handling on removal

Hi, On Tue, 4 Sep 2018 16:34:56 +0200 Ulf Hansson wrote: > On 2 September 2018 at 09:30, Andreas Kemnade wrote: > > after unbinding mmc I get things like this: > > [ 185.294067] mmc1: card 0001 removed > > [ 185.305206] omap_hsmmc 480b4000.mmc: wake IR

Re: Regression in next with filesystem context concept

Hi, On Fri, 7 Sep 2018 09:10:23 -0700 Tony Lindgren wrote: > * David Howells [180907 08:51]: > > Tony Lindgren wrote: > > > > > Looks like next-20180906 now has a regression where mounting > > > root won't work with commit fd0002870b45 ("vfs: Implement a > > > filesystem superblock

Re: [Letux-kernel] [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

Hi, On Thu, 18 Jan 2018 17:47:36 +1100 Johan Hovold wrote: [...] > > > > So to avoid having hardware information spread all over the table at least > > these information would need to be in devicetree. But that also all feels > > like a hack and hard to maintain. > >

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladis, On Tue, 10 Apr 2018 22:56:43 +0200 Ladislav Michl wrote: > Hi Nikolaus, > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > > Hi, > > we just started testing the v4.16 kernel and found the > > device no longer bootable (works with v4.15).

Re: [PATCH 0/7] gnss: add new GNSS subsystem

On Tue, 24 Apr 2018 22:13:19 +0200 Pavel Machek wrote: > Hi! > > > This series adds a new subsystem for GNSS receivers (e.g. GPS > > receivers). > > Actually... I'd just call it GPS subsystem. Yes, GPS is a bit > misleading, but so is GNSS. We'd like Loran to use similar

Re: [PATCH 0/2] mach-omap2: handle autoidle denial

ping. ..after stumbling again about that problem during testing with 4.20-rc1. will retest it there. On Thu, 4 Oct 2018 22:38:15 +0200 Andreas Kemnade wrote: > On the gta04 with a dm3730 omap_hdq does not work properly when the > device enters lower power states. Idling uart1 and 2 is

Re: [PATCH 2/2] arm: omap_hwmod disable ick autoidling when a hwmod requires that

Hi, On Thu, 8 Nov 2018 12:26:08 +0200 Tero Kristo wrote: > On 04/10/2018 23:38, Andreas Kemnade wrote: > > Deny autoidle for hwmods with the OCPIF_SWSUP_IDLE flag, > > that makes hwmods working properly which cannot handle > > autoidle properly in lower power states.

Re: [PATCH 1/2] clk: ti: add a usecount for autoidle

On Thu, 8 Nov 2018 12:36:35 +0200 Tero Kristo wrote: > On 04/10/2018 23:38, Andreas Kemnade wrote: > > We have the scenario that first autoidle is disabled for all clocks, > > then it is disabled for selected ones and then enabled for all. So > > we should have some counting

[PATCH v2 0/3] mach-omap2: handle autoidle denial

logic - check whether clock type is basic Andreas Kemnade (3): clk: ti: add a usecount for autoidle clk: ti: check clock type before doing autoidle ops arm: omap_hwmod disable ick autoidling when a hwmod requires that arch/arm/mach-omap2/omap_hwmod.c | 16 ++ drivers/clk/ti

[PATCH v2 3/3] arm: omap_hwmod disable ick autoidling when a hwmod requires that

in _setup_iclk_autoidle. dss_ick is an example for that. Signed-off-by: Andreas Kemnade --- Comments to v1 to this patch were worked into a new 2/3 --- arch/arm/mach-omap2/omap_hwmod.c | 16 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/arch/arm/mach-omap2

[PATCH v2 2/3] clk: ti: check clock type before doing autoidle ops

Code might use autoidle api with clocks not being omap2 clocks, so check if clock type is not basic Signed-off-by: Andreas Kemnade --- New in v2 --- drivers/clk/ti/autoidle.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/clk/ti/autoidle.c b/drivers

[PATCH v2 1/3] clk: ti: add a usecount for autoidle

Multiple users might deny autoidle on a clock. So we should have some counting here, also according to the comment in _setup_iclk_autoidle(). Also setting autoidle regs is not atomic, so there is another reason for locking. Signed-off-by: Andreas Kemnade --- Changes since v1: - use spinlocks

[PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree

proceeding further it should be checked if the general way of doing things is right. Signed-off-by: Andreas Kemnade --- drivers/bluetooth/hci_h4.c | 78 ++ 1 file changed, 78 insertions(+) diff --git a/drivers/bluetooth/hci_h4.c b/drivers/bluetooth/hci_h4

Re: [Letux-kernel] [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree

On Mon, 12 Nov 2018 18:17:38 -0600 Rob Herring wrote: > On Mon, Nov 12, 2018 at 4:27 PM Sebastian Reichel > wrote: > > > > Hi, > > > > On Mon, Nov 12, 2018 at 10:19:02PM +0100, H. Nikolaus Schaller wrote: > > > > Am 12.11.2018 um 21:59 schrieb Andrea

Re: [Letux-kernel] [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree

On Wed, 14 Nov 2018 08:51:17 +0100 Marcel Holtmann wrote: > Hi Andreas, > > >>>>> Am 12.11.2018 um 21:59 schrieb Andreas Kemnade : > >>>>> On Sun, 11 Nov 2018 03:46:48 +0100 > >>>>> Sebastian Reichel wrote: > >>

Re: [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree

Hi, On Sun, 11 Nov 2018 03:46:48 +0100 Sebastian Reichel wrote: > Hi, > > On Sun, Nov 11, 2018 at 12:20:34AM +0100, Andreas Kemnade wrote: > > This is a first try to be able to use h4 devices specified in > > the devicetree, so you do not need to call hciattach and > &

Re: [PATCH RFC 1/2] clk: ti: add a usecount for autoidle

Hi, On Thu, 4 Oct 2018 17:40:06 +0300 Tero Kristo wrote: > On 04/10/18 08:51, Andreas Kemnade wrote: > > We have the scenario that first autoidle is disabled for all clocks, > > then it is disabled for selected ones and then enabled for all. So > > we should have som

[PATCH 2/2] arm: omap_hwmod disable ick autoidling when a hwmod requires that

in _setup_iclk_autoidle. dss_ick is an example for that. Signed-off-by: Andreas Kemnade --- arch/arm/mach-omap2/omap_hwmod.c | 16 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c index bb641e6c93d0

[PATCH 0/2] mach-omap2: handle autoidle denial

- deny_idle/allow_idle calls moved to clock enable/disable of the individual modules Andreas Kemnade (2): clk: ti: add a usecount for autoidle arm: omap_hwmod disable ick autoidling when a hwmod requires that arch/arm/mach-omap2/omap_hwmod.c | 16 drivers/clk/ti/autoidle.c

[PATCH 1/2] clk: ti: add a usecount for autoidle

We have the scenario that first autoidle is disabled for all clocks, then it is disabled for selected ones and then enabled for all. So we should have some counting here, also according to the comment in _setup_iclk_autoidle() Signed-off-by: Andreas Kemnade --- drivers/clk/ti/autoidle.c | 32

Re: [PATCH RESEND] twl4030_charger: fix charging current out-of-bounds

Hi Pavel, On Sun, 30 Sep 2018 22:16:42 +0200 Pavel Machek wrote: > On Mon 2018-09-17 07:20:35, Andreas Kemnade wrote: > > the charging current uses unsigned int variables, if we step back > > if the current is still low, we would run into negative which > > means setting

[PATCH RFC 1/2] clk: ti: add a usecount for autoidle

We have the scenario that first autoidle is disabled for all clocks, then it is disabled for selected ones and then enabled for all. So we should have some counting here, also according to the comment in _setup_iclk_autoidle() Signed-off-by: Andreas Kemnade --- drivers/clk/ti/autoidle.c | 20

[PATCH RFC 2/2] arm: mach-omap2: setup iclk autoidle according to flags

explicitly because there might be clocks which do not support that operation and it is enabled afterwards in arm/mach-omap2/pm.c anyways. Signed-off-by: Andreas Kemnade --- arch/arm/mach-omap2/omap_hwmod.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-omap2

[PATCH RFC 0/2] mach-omap2: handle autoidle denial

changing order. Andreas Kemnade (2): clk: ti: add a usecount for autoidle arm: mach-omap2: setup iclk autoidle according to flags arch/arm/mach-omap2/omap_hwmod.c | 8 ++-- drivers/clk/ti/autoidle.c| 20 include/linux/clk/ti.h | 1 + 3 files changed

[PATCH v2] phy: phy-twl4030-usb: fix denied runtime access

the device is woken up from suspend by plugging in usb. Signed-off-by: Andreas Kemnade --- Changes in v2: * use pm suspend/resume callback instead of delayed_work as suggested by Dmitry drivers/phy/ti/phy-twl4030-usb.c | 29 + 1 file changed, 29 insertions(+) diff --git

[PATCH] w1: omap-hdq: fix missing bus unregister at removal

] Code: bad PC value [ 128.064697] ---[ end trace af066e33c0e14119 ]--- Cc: Signed-off-by: Andreas Kemnade --- drivers/w1/masters/omap_hdq.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/w1/masters/omap_hdq.c b/drivers/w1/masters/omap_hdq.c index 83fc9aab34e8..3099052e1243 100644

[PATCH] ARM: dts: omap3-gta04: add pulldown/up settings for twl4030 gpio

Pullup and down settings were missing, so add them to avoid floating pins and make headset detection working. Signed-off-by: Andreas Kemnade --- arch/arm/boot/dts/omap3-gta04.dtsi | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm

Re: [PATCH] ARM: dts: gta04: add serial console wakeup irq

Hi Tony, On Mon, 24 Sep 2018 15:03:45 -0700 Tony Lindgren wrote: > * Andreas Kemnade [180923 08:12]: > > This enables the possibility to have more aggressive runtime pm > > by providing proper wakeup irq for the serial console. > > Thanks applying to omap-for-v4.20/dt.

[PATCH] ARM: dts: gta04: add serial console wakeup irq

This enables the possibility to have more aggressive runtime pm by providing proper wakeup irq for the serial console. Signed-off-by: Andreas Kemnade --- arch/arm/boot/dts/omap3-gta04.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot

[PATCH RFC 5/5] dt-bindings: gnss: add lna-supply property

Add lna-supply property. Signed-off-by: Andreas Kemnade --- Documentation/devicetree/bindings/gnss/sirfstar.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/gnss/sirfstar.txt b/Documentation/devicetree/bindings/gnss/sirfstar.txt index 1be7597ae884

[PATCH 2/5] gnss: sirf: power on logic for devices without wakeup signal

, because the reaction on serial line is slower and are in line with previous patches by Neil Brown and H. Nikolaus Schaller . Signed-off-by: Andreas Kemnade --- drivers/gnss/sirf.c | 97 +++-- 1 file changed, 65 insertions(+), 32 deletions(-) diff

[PATCH 3/5] dt-bindings: gnss: add w2sg0004 compatible string

Add w2sg0004 compatible string since devices without wakeup pins are now supported. Signed-off-by: Andreas Kemnade --- Documentation/devicetree/bindings/gnss/sirfstar.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/gnss/sirfstar.txt b/Documentation

[PATCH RFC 4/5] gnss: sirf: add a separate supply for a lna

Devices might have a separate lna between antenna output of the gps chip and the antenna which might have a separate supply Signed-off-by: Andreas Kemnade --- drivers/gnss/sirf.c | 15 +++ 1 file changed, 15 insertions(+) diff --git a/drivers/gnss/sirf.c b/drivers/gnss/sirf.c index

[PATCH 0/5] gnss: sirf: add support for w2sg0004 + lna

of that chip without an additional lna power supply can already benefit from it if we should do more discussion first. I just kept them together so that the full picture can be seen. Andreas Kemnade (5): gnss: sirf: write data to gnss only when the gnss device is open gnss: sirf: power on logic

[PATCH 1/5] gnss: sirf: write data to gnss only when the gnss device is open

The api forbids writing data there otherwise. Prepare for the serdev_open()/close() being a part of runtime pm. Signed-off-by: Andreas Kemnade --- drivers/gnss/sirf.c | 16 +++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/drivers/gnss/sirf.c b/drivers/gnss/sirf.c

Re: [Letux-kernel] [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree

Hi Marcel, On Wed, 14 Nov 2018 08:51:17 +0100 Marcel Holtmann wrote: [...[ > Btw. I see nothing standing in the way of merging btuart.c driver and then go > from there. Either I dig this out and submit or someone else does. > Do you mean this? https://patchwork.kernel.org/patch/10490651/

Re: [PATCH 1/5] gnss: sirf: write data to gnss only when the gnss device is open

On Wed, 5 Dec 2018 15:47:39 +0100 Johan Hovold wrote: > On Sun, Nov 18, 2018 at 10:57:57PM +0100, Andreas Kemnade wrote: > > The api forbids writing data there otherwise. Prepare for the > > serdev_open()/close() being a part of runtime pm. > > > > Sig

Re: [PATCH 2/5] gnss: sirf: power on logic for devices without wakeup signal

On Wed, 5 Dec 2018 16:01:16 +0100 Johan Hovold wrote: > On Sun, Nov 18, 2018 at 10:57:58PM +0100, Andreas Kemnade wrote: > > Some Wi2Wi devices do not have a wakeup output, so device state can > > only be indirectly detected by looking whether there is communitcation > >

Re: [PATCH v2 2/3] clk: ti: check clock type before doing autoidle ops

On Mon, 3 Dec 2018 07:39:10 -0800 Tony Lindgren wrote: > * Stephen Boyd [181130 23:52]: > > Quoting Tony Lindgren (2018-11-30 07:37:29) > > > Hi, > > > > > > * Tero Kristo [181130 09:21]: > > > > On 30/11/2018 09:57, Stephen Boyd wrote: > > > > > No that is not preferred. Can the

  1   2   3   4   5   >