Re: i915 IVB hangup after resume from s2mem since v6.6.x

On Mon, May 06, 2024 at 09:42:18PM +0200, Lukas Wunner wrote: > On Mon, May 06, 2024 at 08:43:43PM +0200, Johannes Stezenbach wrote: > > so, git bisect pointed to: > > > > commit 701d2054fa317188cd4039c84e72c73254013b23 > > Author: Thomas Zimmermann > > Date:

Re: i915 IVB hangup after resume from s2mem since v6.6.x

Hi, so, git bisect pointed to: commit 701d2054fa317188cd4039c84e72c73254013b23 Author: Thomas Zimmermann Date: Tue Jun 13 13:07:13 2023 +0200 fbdev: Make support for userspace interfaces configurable Add Kconfig option CONFIG_FB_DEVICE and make the virtual fbdev ... I think

Re: i915 IVB hangup after resume from s2mem since v6.6.x

Hi Jani, thank you for the quick response. Currently the machine is in use and I cannot crash and reboot it at will. I will file the bug report in the next days when I gathered the requested logs. I might as well git bisect it, otherwise I guess the root cause would be hard to find. Thanks,

i915 IVB hangup after resume from s2mem since v6.6.x

Hi, I updated the Linux kernel on an old machine from v6.5.9 to current v6.8.8 and found the display failed after resume from suspend to RAM. Then I tried v6.7.9 and v6.6.29, both also failed. v6.5.9 works. - display connected via display port: hangup - I also tried HDMI with v6.6.29: garbage

Bug#1057404: android-sdk-platform-tools-common: udev rules break printing

Package: android-sdk-platform-tools-common Version: 28.0.2+9 Severity: normal Dear Maintainer, CUPS printing to my USB attached printer stopped working (with error message "cannot send data to the printer"). After some debug I found the issue is caused by wrong ownership of the device node, it

Re: [Dnsmasq-discuss] [bisected] re-reading resolv.conf bug

On Wed, Jan 05, 2022 at 04:12:21PM +, Simon Kelley wrote: > > I did check it and it's a bit of a mess. Reverting efea282396 only > coincidentally fixes the problem, knowing that it does made finding the > real problem much easier, so thanks for that information. > > I believe the real fix is

[Dnsmasq-discuss] [bisected] re-reading resolv.conf bug

Hi Simon, commit efea282396 "Fix logic in add_update_server() to make optimisation actually optimise." introduced a bug when re-reading resolv.conf after changes. Found by git bisect and confirmed by reverting efea282396 on top of current git 011f8cf1d011. The issue happens when

Re: [PATCH v2] Revert "drm/fb-helper: improve DRM fbdev emulation device names"

even when this lead to silly names like the > one mentioned above. I would like to ask about the fate of this patch. It doesn't seem to have been picked up by anyone, does it? Thanks, Johannes > Fixes: b3484d2b03e4 ("drm/fb-helper: improve DRM fbdev emulation device > names")

Re: [Dnsmasq-discuss] dnsmasq and VPN client updates resolv.conf with multiple nameservers

On Thu, Nov 04, 2021 at 07:46:18AM +0100, Geert Stappers via Dnsmasq-discuss wrote: > On Wed, Nov 03, 2021 at 11:45:15PM +0100, Johannes Stezenbach wrote: > > > > I've tried current git version v2.87test4-2-g9560658c5ba2. > > > > Usually /run/dnsmasq/resolv.con

[Dnsmasq-discuss] dnsmasq misreads resolv.conf with multiple nameservers

Hi, I've tried current git version v2.87test4-2-g9560658c5ba2. Usually /run/dnsmasq/resolv.conf has only one entry for my home Wifi router. When I enable a VPN connection two more entries are added, but dnsmasq doesn't read it correctly. Real: nameserver 10.x.xx.60 nameserver 10.x.xx.75

Re: [Intel-gfx] [bisected] suspend broken by DRM fbdev name change on i915 IVB

Hi Javier, On Thu, Oct 07, 2021 at 03:01:46PM +0200, Javier Martinez Canillas wrote: > Yes, the change was just cosmetic because we had confusing names such as > "simpledrmdrmfb". When it was proposed, the agreement was that /proc/fb > shouldn't be considered an ABI but now we found that people

Re: [Intel-gfx] [bisected] suspend broken by DRM fbdev name change on i915 IVB

Hi Javier, On Thu, Oct 07, 2021 at 03:01:46PM +0200, Javier Martinez Canillas wrote: > Yes, the change was just cosmetic because we had confusing names such as > "simpledrmdrmfb". When it was proposed, the agreement was that /proc/fb > shouldn't be considered an ABI but now we found that people

[bisected] suspend broken by DRM fbdev name change on i915 IVB

Hi, yesterday I updated the kernel from 5.13.7 to 5.14.9 and found it broke suspend-to-RAM. The machine displays a few messages on text console after resume but hangs when switching to X11. The hardware: Asus P8H77-V with Intel Core i5-3550 CPU, display connected via DP. DP1 connected primary

[Intel-gfx] [bisected] suspend broken by DRM fbdev name change on i915 IVB

Hi, yesterday I updated the kernel from 5.13.7 to 5.14.9 and found it broke suspend-to-RAM. The machine displays a few messages on text console after resume but hangs when switching to X11. The hardware: Asus P8H77-V with Intel Core i5-3550 CPU, display connected via DP. DP1 connected primary

Re: [Dnsmasq-discuss] REFUSED after dropped packets

On Mon, Sep 27, 2021 at 10:45:25PM +0100, Simon Kelley wrote: > > I think that this is a 2.86 problem. There are two cases when dnsmasq > will try another server with the same query: > > 1) When a client retries the query. > 2) When the first server returns REFUSED. > > In the second case, it's

Re: [Dnsmasq-discuss] Permission denied on logfile

On Tue, Sep 21, 2021 at 09:40:17PM +0100, Simon Kelley wrote: > On 21/09/2021 20:54, Johannes Stezenbach wrote: > > This works the first time, but fails after dnsmasq is restarted: > > dnsmasq: cannot open log /tmp/dnsmasq.log: Permission denied > > > > $ ls -l /tmp/d

[Dnsmasq-discuss] Permission denied on logfile

Hi, a minor issue I noticed while debugging: I added this to the dnsmasq command line: --log-queries=extra --log-debug --log-facility=/tmp/dnsmasq.log (actually set in DNSMASQ_OPTS in /etc/default/dnsmasq in Debian) This works the first time, but fails after dnsmasq is restarted: dnsmasq:

Re: [Dnsmasq-discuss] REFUSED after dropped packets

On Tue, Sep 21, 2021 at 09:38:41AM +0100, Simon Kelley wrote: > The culprit in --strict-order. > > Comment from the code to save my re-typing: > > /* In strict order mode, there must be a server later in the list >left to send to, otherwise without the forwardall mechanism, >code further

[Dnsmasq-discuss] REFUSED after dropped packets

Hi, after recent update to 2.86 on Debian sid I'm seeing failures in name resolution. I think the issue is that my Wifi connection is currently flaky (another problem to solve...) and the DNS reply gets lost. After that dnsmasq reports REFUSED, e.g.: Sep 20 21:06:38 dnsmasq[18805]: 55

Re: patch/rfc: gui_beval issue with gtk3

Hi Bram, On Fri, Jun 11, 2021 at 11:53:16AM +0200, Johannes Stezenbach wrote: > I'm suffering from an annoying issue with ballooneval as > used by the taglist plugin. When using gvim built with --enable-gui=gtk3 > the balloon sometimes does not hide when the gvim window loses >

patch/rfc: gui_beval issue with gtk3

(resend, CONTRIBUTING.md points to http://www.vim.org/maillist.php#vim-dev but mail to vim-...@vim.org apparently does not make it to the list) Hi, I'm suffering from an annoying issue with ballooneval as used by the taglist plugin. When using gvim built with --enable-gui=gtk3 the balloon

Bug#985972: mc: cannot view rar archives with unrar version 6

Package: mc Version: 3:4.8.26-1 Severity: normal Tags: patch Dear Maintainer, viewing rar archives worked in the past but stopped at some point, the reason is that unrar-nonfree has been upgraded from 5.9.4-1 to 6.0.3-1 (and now 6.0.4-1). This is not handled by the extfs/urar script but can be

Bug#985046: mc: cannot view zip file containing pdf

Package: mc Version: 3:4.8.26-1 Severity: normal Dear Maintainer, since the last mc update I cannot view zip files containing pdf files anymore, this seems to be related to mc's use of "file -z". I confirmed this happens when the ~/.config/mc/mc.ext is removed and thus /etc/mc/mc.ext is used. $

Bug#981485: offlineimap3: crash when uploading locally created no-utf-8 encoded message

Hi Sudip, On Fri, Feb 19, 2021 at 03:59:35PM +, Sudip Mukherjee wrote: > On Mon, Feb 1, 2021 at 10:57 PM Sudip Mukherjee > wrote: > > > > Control: forwarded -1 https://github.com/OfflineIMAP/offlineimap3/issues/43 > > Will it be possible to test the change at >

Bug#981485: offlineimap3: crash when uploading locally created no-utf-8 encoded message

Package: offlineimap3 Version: 0.0~git20210105.00d395b+dfsg-2 Severity: important Dear Maintainer, I sent a message composed in mutt, afterwards offlineimap3 crashed while trying to upload the sent message to IMAP server with message "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in

Bug#945920: Minified Javascript

Dear Maintainer, > The status so far is that we have a patch that solves the problem by > re-enabling [tracing][1], but the reason that tracing was disabled in the > first place is because it depends on minified javascript. Personally I always regretted that Debian chose to remove the trace

Bug#945920: Minified Javascript

Dear Maintainer, > The status so far is that we have a patch that solves the problem by > re-enabling [tracing][1], but the reason that tracing was disabled in the > first place is because it depends on minified javascript. Personally I always regretted that Debian chose to remove the trace

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

I now reported it upstream: https://bugs.ghostscript.com/show_bug.cgi?id=701949 Johannes

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

I now reported it upstream: https://bugs.ghostscript.com/show_bug.cgi?id=701949 Johannes

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

Now confirmed (by printing the CUPS test page) that the bug is still present in 9.50~dfsg-2, and that the workaround patch still applies and still works. Johannes

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

Now confirmed (by printing the CUPS test page) that the bug is still present in 9.50~dfsg-2, and that the workaround patch still applies and still works. Johannes

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

ghostscript_9.50~dfsg-2 packages have been uploaded, with this bug probably still unfixed and unknown to upstream. I was not able to actually test my printer with 9.50 yet, but changes in upstream git don't seem to address this bug, and it's not in upstream butracker. Question to the package

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

ghostscript_9.50~dfsg-2 packages have been uploaded, with this bug probably still unfixed and unknown to upstream. I was not able to actually test my printer with 9.50 yet, but changes in upstream git don't seem to address this bug, and it's not in upstream butracker. Question to the package

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

Package: ghostscript Version: 9.28~~rc4~dfsg-1 Severity: important Tags: upstream Dear Maintainer, my Samsung ML-2250 printer stopped to work, it outputs a page with this error message: PCL6 ERROR - sb_count != -128 POSITION : 0xbc8 (3016) SYSTEM : XLPGP/xl_pattern LINE :

Bug#941864: cups: pxlmono fails to print on Samsung ML-2250 with 9.28rc

Package: ghostscript Version: 9.28~~rc4~dfsg-1 Severity: important Tags: upstream Dear Maintainer, my Samsung ML-2250 printer stopped to work, it outputs a page with this error message: PCL6 ERROR - sb_count != -128 POSITION : 0xbc8 (3016) SYSTEM : XLPGP/xl_pattern LINE :

Bug#933514: tmux: Screen garbling in ncurses apps

On Thu, Aug 01, 2019 at 10:28:26PM +0200, Romain Francoise wrote: > A patch for this is now available in the upstream bug tracker > (https://github.com/tmux/tmux/issues/1861) and I have tested it > successfully using the Mutt recipe from #933572. The issue is not fixed for me with mutt in tmux

Bug#922239: libpam0g 1.3.1-2 upgrade kills xdm

Package: libpam0g Version: 1.3.1-2 Severity: critical Justification: causes serious data loss Dear Maintainer, my X session was just killed during update, I could capture the output because aptitude was running inside tmux: Unpacking libpam0g:amd64 (1.3.1-2) over (1.1.8-4) ... Setting up

Bug#922239: libpam0g 1.3.1-2 upgrade kills xdm

Package: libpam0g Version: 1.3.1-2 Severity: critical Justification: causes serious data loss Dear Maintainer, my X session was just killed during update, I could capture the output because aptitude was running inside tmux: Unpacking libpam0g:amd64 (1.3.1-2) over (1.1.8-4) ... Setting up

Re: Regression found (Stop-marking-clocks-as-CLK_IS_CRITICAL)

On Thu, Jan 17, 2019 at 01:05:35PM +0100, Hans de Goede wrote: > On 17-01-19 10:12, Dean Wallace wrote: > > On 17-01-19, Mogens Jensen wrote: > > > Kernel is compiled with SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH and the > > > quirk seems to have fixed the problem caused by commit 648e921888ad > >

Re: 4.18.16: memory leak in sta_set_sinfo

On Mon, Oct 22, 2018 at 10:25:07AM +0200, Johannes Berg wrote: > On Mon, 2018-10-22 at 10:02 +0200, Johannes Stezenbach wrote: > > > > [<b7b13d1a>] sta_set_sinfo+0x634/0x900 [mac80211] > > [<a74db622>] ieee80211_get_station+0x50/0x70 [mac

4.18.16: memory leak in sta_set_sinfo

Hi, I used 4.18.11 for a while and noticed a memleak showing in slabtop as kmalloc-2048. Then I updated to 4.18.16 and enabled kmemleak, it dumps this: unreferenced object 0xa10a5cc49800 (size 2048): comm "conky", pid 2734, jiffies 4295635396 (age 454.650s) hex dump (first 32 bytes):

Re: [PATCH] PM: Document rules on using pm_runtime_resume() in system suspend callbacks

On Thu, Sep 21, 2017 at 02:39:30AM +0200, Rafael J. Wysocki wrote: > On Wed, Sep 20, 2017 at 6:27 PM, Johannes Stezenbach <j...@sig21.net> wrote: > > > > E.g. an audio codec could keep running > > while the i2c bus used to program its registers can be runtime suspende

Re: [PATCH] PM: Document rules on using pm_runtime_resume() in system suspend callbacks

On Thu, Sep 21, 2017 at 02:39:30AM +0200, Rafael J. Wysocki wrote: > On Wed, Sep 20, 2017 at 6:27 PM, Johannes Stezenbach wrote: > > > > E.g. an audio codec could keep running > > while the i2c bus used to program its registers can be runtime suspended. > > If this

Re: [PATCH] PM: Document rules on using pm_runtime_resume() in system suspend callbacks

On Wed, Sep 20, 2017 at 04:01:32PM +0200, Rafael J. Wysocki wrote: > On Wed, Sep 20, 2017 at 2:28 PM, Ulf Hansson wrote: > > On 20 September 2017 at 02:26, Rafael J. Wysocki wrote: > >> > >> Second, leaving devices in runtime suspend in the "suspend"

Re: [PATCH] PM: Document rules on using pm_runtime_resume() in system suspend callbacks

On Wed, Sep 20, 2017 at 04:01:32PM +0200, Rafael J. Wysocki wrote: > On Wed, Sep 20, 2017 at 2:28 PM, Ulf Hansson wrote: > > On 20 September 2017 at 02:26, Rafael J. Wysocki wrote: > >> > >> Second, leaving devices in runtime suspend in the "suspend" phase of system > >> suspend is fishy even

Re: [PATCH 2/3] input/keyboard: Add support for Dollar Cove TI power button

On Tue, Aug 22, 2017 at 12:58:07PM +0200, Takashi Iwai wrote: > I updated the patches and now pushed to topic/dollar-cove-ti-4.13-v2 > branch. Will resubmit v2 (tomorrow or later) once after gathering > reviews. FWIW I tested current Linus's master + topic/dollar-cove-ti-4.13-v2 +

Re: [PATCH 2/3] input/keyboard: Add support for Dollar Cove TI power button

On Tue, Aug 22, 2017 at 12:58:07PM +0200, Takashi Iwai wrote: > I updated the patches and now pushed to topic/dollar-cove-ti-4.13-v2 > branch. Will resubmit v2 (tomorrow or later) once after gathering > reviews. FWIW I tested current Linus's master + topic/dollar-cove-ti-4.13-v2 +

[Savannah-register-public] [task #14532] Submission of FRITZ!Box voicebox converter

Follow-up Comment #4, task #14532 (project administration): Hi, it seems I might have a wrong understanding of Savannah's purpose, even after I spent much time reading through the documentation linked on the main page and to the left under Site Help. I was searching for a place to publish my

[Savannah-register-public] [task #14532] Submission of FRITZ!Box voicebox converter

Follow-up Comment #2, task #14532 (project administration): You have a point, but all great projects start as quick hacks ;-) FritzBoxes have millions of users in Germany so I expect people might send patches to improve it, posting it in a blog is a dead end. I also will disable all the savannah

[Savannah-register-public] [task #14532] Submission of FRITZ!Box voicebox converter

URL: Summary: Submission of FRITZ!Box voicebox converter Project: Savannah Administration Submitted by: js2 Submitted on: Fri 02 Jun 2017 08:12:22 AM UTC Should Start On: Fri 02 Jun 2017

[Savannah-register-public] [task #14530] Submission of DDC/CI Python script

Follow-up Comment #2, task #14530 (project administration): Hi Pavel, I'm attaching the updated README file. Thanks for the review! (file #40829) ___ Additional Item Attachment: File name: README Size:5 KB

[Savannah-register-public] [task #14530] Submission of DDC/CI Python script

URL: Summary: Submission of DDC/CI Python script Project: Savannah Administration Submitted by: js2 Submitted on: Tue 30 May 2017 02:40:07 PM UTC Should Start On: Tue 30 May 2017 12:00:00

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 05:58:26PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 04:42:43PM +0100, Johannes Stezenbach wrote: > > On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote: > > > Is the model Asus E200HA? Something like this (sor

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 05:58:26PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 04:42:43PM +0100, Johannes Stezenbach wrote: > > On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote: > > > Is the model Asus E200HA? Something like this (sor

Re: Cherryview wake up events

On Fri, Feb 03, 2017 at 12:00:00PM +0200, Mika Westerberg wrote: > Just for book keeping purposes, can you file a kernel.org bugzilla bug > about this and add all the necessary information, and your patches > there? You can assign the bug directly to me. I filed it but cannot assign it, added you

Re: Cherryview wake up events

On Fri, Feb 03, 2017 at 12:00:00PM +0200, Mika Westerberg wrote: > Just for book keeping purposes, can you file a kernel.org bugzilla bug > about this and add all the necessary information, and your patches > there? You can assign the bug directly to me. I filed it but cannot assign it, added you

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 05:58:26PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 04:42:43PM +0100, Johannes Stezenbach wrote: > > On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote: > > > Is the model Asus E200HA? Something like this (sor

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 05:58:26PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 04:42:43PM +0100, Johannes Stezenbach wrote: > > On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote: > > > Is the model Asus E200HA? Something like this (sor

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote: > OK, I guess it is easier if I just order one of those machines here and > figure out how to get the PMIC driver working. Oh, I assumed the bottleneck is developer time, not lack of hardware... > Is the model Asus E200HA?

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote: > OK, I guess it is easier if I just order one of those machines here and > figure out how to get the PMIC driver working. Oh, I assumed the bottleneck is developer time, not lack of hardware... > Is the model Asus E200HA?

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 04:26:18PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 02:52:57PM +0100, Johannes Stezenbach wrote: > > Looking at 0002-GPIO-Adding-AXP288-PMIC-GPIO-driver.patch from > > ProductionKernelQuilts, > > it doesn't seem hard to do the

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 04:26:18PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 02:52:57PM +0100, Johannes Stezenbach wrote: > > Looking at 0002-GPIO-Adding-AXP288-PMIC-GPIO-driver.patch from > > ProductionKernelQuilts, > > it doesn't seem hard to do the

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 02:16:39PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 01:35:08PM +0200, Mika Westerberg wrote: > > On Thu, Feb 02, 2017 at 12:12:22PM +0100, Johannes Stezenbach wrote: > > > On Thu, Feb 02, 2017 at 12:31:22PM +0200, Mika Westerberg wrote: >

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 02:16:39PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 01:35:08PM +0200, Mika Westerberg wrote: > > On Thu, Feb 02, 2017 at 12:12:22PM +0100, Johannes Stezenbach wrote: > > > On Thu, Feb 02, 2017 at 12:31:22PM +0200, Mika Westerberg wrote: >

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 12:31:22PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 10:52:00AM +0100, Johannes Stezenbach wrote: > > OperationRegion (GPOP, GeneralPurposeIo, Zero, 0x0100) > > Field (GPOP, ByteAcc, N

Re: Cherryview wake up events

On Thu, Feb 02, 2017 at 12:31:22PM +0200, Mika Westerberg wrote: > On Thu, Feb 02, 2017 at 10:52:00AM +0100, Johannes Stezenbach wrote: > > OperationRegion (GPOP, GeneralPurposeIo, Zero, 0x0100) > > Field (GPOP, ByteAcc, N

Re: Cherryview wake up events

Hi Mika, On Tue, Jan 31, 2017 at 03:37:40PM +0100, Johannes Stezenbach wrote: > - Powerbutton driver seems simple enough, the only specialty > of the TI dcove PB driver is the workarond for lost button > press event after resume. However, I still don't see how > the PB would c

Re: Cherryview wake up events

Hi Mika, On Tue, Jan 31, 2017 at 03:37:40PM +0100, Johannes Stezenbach wrote: > - Powerbutton driver seems simple enough, the only specialty > of the TI dcove PB driver is the workarond for lost button > press event after resume. However, I still don't see how > the PB would c

Re: Cherryview wake up events

Hi Andy and Mika, On Tue, Jan 31, 2017 at 12:05:07AM +0200, Andy Shevchenko wrote: > On Mon, Jan 30, 2017 at 10:57 PM, Johannes Stezenbach <j...@sig21.net> wrote: > > > > I checked the reference source code, my impression is the > > TI Dollar Cove and and AXP288 are co

Re: Cherryview wake up events

Hi Andy and Mika, On Tue, Jan 31, 2017 at 12:05:07AM +0200, Andy Shevchenko wrote: > On Mon, Jan 30, 2017 at 10:57 PM, Johannes Stezenbach wrote: > > > > I checked the reference source code, my impression is the > > TI Dollar Cove and and AXP288 are completely different

Re: Cherryview wake up events

On Fri, Jan 27, 2017 at 02:30:58PM +0100, Johannes Stezenbach wrote: > On Fri, Jan 27, 2017 at 03:21:22PM +0200, Andy Shevchenko wrote: > > On Fri, Jan 27, 2017 at 1:38 PM, Johannes Stezenbach <j...@sig21.net> wrote: > > > On Fri, Jan 27, 2017 at 12:56:53AM +020

Re: Cherryview wake up events

On Fri, Jan 27, 2017 at 02:30:58PM +0100, Johannes Stezenbach wrote: > On Fri, Jan 27, 2017 at 03:21:22PM +0200, Andy Shevchenko wrote: > > On Fri, Jan 27, 2017 at 1:38 PM, Johannes Stezenbach wrote: > > > On Fri, Jan 27, 2017 at 12:56:53AM +0200, Andy Shevchenko wrote: > &g

Re: Cherryview wake up events

On Fri, Jan 27, 2017 at 03:21:22PM +0200, Andy Shevchenko wrote: > On Fri, Jan 27, 2017 at 1:38 PM, Johannes Stezenbach <j...@sig21.net> wrote: > > On Fri, Jan 27, 2017 at 12:56:53AM +0200, Andy Shevchenko wrote: > > > And the same info is also in sysfs: > > > &

Re: Cherryview wake up events

On Fri, Jan 27, 2017 at 03:21:22PM +0200, Andy Shevchenko wrote: > On Fri, Jan 27, 2017 at 1:38 PM, Johannes Stezenbach wrote: > > On Fri, Jan 27, 2017 at 12:56:53AM +0200, Andy Shevchenko wrote: > > > And the same info is also in sysfs: > > > > # cat > > /s

Re: Cherryview wake up events

On Fri, Jan 27, 2017 at 12:56:53AM +0200, Andy Shevchenko wrote: > > I'm reading your long thread about the issue. Thanks for taking the time! > > but excluded CONFIG_MFD_AXP20X based on \_SB.PIC0.I2C7.PMI1._STA returning > > 0 in acpidbg, > > but \_SB.PIC0.I2C7.PMI1._STA returns 0xf > > Did

Re: Cherryview wake up events

On Fri, Jan 27, 2017 at 12:56:53AM +0200, Andy Shevchenko wrote: > > I'm reading your long thread about the issue. Thanks for taking the time! > > but excluded CONFIG_MFD_AXP20X based on \_SB.PIC0.I2C7.PMI1._STA returning > > 0 in acpidbg, > > but \_SB.PIC0.I2C7.PMI1._STA returns 0xf > > Did

Re: Cherryview wake up events

On Tue, Jan 24, 2017 at 04:28:29PM +0200, Andy Shevchenko wrote: > They probably release just almost all One Big Ugly patch from official > BSP, which by some reason, includes all Intel MID SoCs, Baytrail. > I think I know how Dollar Cove related code ended up there. But that > all stuff is a

Re: Cherryview wake up events

On Tue, Jan 24, 2017 at 04:28:29PM +0200, Andy Shevchenko wrote: > They probably release just almost all One Big Ugly patch from official > BSP, which by some reason, includes all Intel MID SoCs, Baytrail. > I think I know how Dollar Cove related code ended up there. But that > all stuff is a

Re: Cherryview wake up events

On Tue, Jan 24, 2017 at 01:14:16PM +0200, Andy Shevchenko wrote: > On Tue, Jan 24, 2017 at 11:41 AM, Johannes Stezenbach <j...@sig21.net> wrote: > > Meanwhile I found out the TI PMIC and power button drivers > > has been published as part of the Asus ZenFone Zoom (ZX551ML) &g

Re: Cherryview wake up events

On Tue, Jan 24, 2017 at 01:14:16PM +0200, Andy Shevchenko wrote: > On Tue, Jan 24, 2017 at 11:41 AM, Johannes Stezenbach wrote: > > Meanwhile I found out the TI PMIC and power button drivers > > has been published as part of the Asus ZenFone Zoom (ZX551ML) > > Android ke

Re: Cherryview wake up events

Hi, On Mon, Dec 05, 2016 at 01:06:08PM +0200, Mika Westerberg wrote: > On Sun, Dec 04, 2016 at 07:52:19PM +0100, Johannes Stezenbach wrote: > > On Wed, Oct 05, 2016 at 04:05:11PM +0300, Mika Westerberg wrote: > > > On Wed, Oct 05, 2016 at 02:46:48PM +0200, Johanne

Re: Cherryview wake up events

Hi, On Mon, Dec 05, 2016 at 01:06:08PM +0200, Mika Westerberg wrote: > On Sun, Dec 04, 2016 at 07:52:19PM +0100, Johannes Stezenbach wrote: > > On Wed, Oct 05, 2016 at 04:05:11PM +0300, Mika Westerberg wrote: > > > On Wed, Oct 05, 2016 at 02:46:48PM +0200, Johanne

Re: Cherryview wake up events

Hi, On Wed, Oct 05, 2016 at 04:05:11PM +0300, Mika Westerberg wrote: > On Wed, Oct 05, 2016 at 02:46:48PM +0200, Johannes Stezenbach wrote: > > On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote: > > > David (CC'd) is working on getting the Dollar Cove PMIC drive

Re: Cherryview wake up events

Hi, On Wed, Oct 05, 2016 at 04:05:11PM +0300, Mika Westerberg wrote: > On Wed, Oct 05, 2016 at 02:46:48PM +0200, Johannes Stezenbach wrote: > > On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote: > > > David (CC'd) is working on getting the Dollar Cove PMIC drive

Re: [PATCH v2 18/31] gp8psk: don't do DMA on stack

On Sun, Nov 06, 2016 at 11:51:14AM -0800, VDR User wrote: > I applied this patch to the 4.8.4 kernel driver (that I'm currently > running) and it caused nothing but "frontend 0/0 timed out while > tuning". Is there another patch that should be used in conjunction > with this? If not, this patch

Re: [PATCH v2 18/31] gp8psk: don't do DMA on stack

On Sun, Nov 06, 2016 at 11:51:14AM -0800, VDR User wrote: > I applied this patch to the 4.8.4 kernel driver (that I'm currently > running) and it caused nothing but "frontend 0/0 timed out while > tuning". Is there another patch that should be used in conjunction > with this? If not, this patch

Re: [PATCH v2 18/31] gp8psk: don't do DMA on stack

On Sun, Nov 06, 2016 at 11:51:14AM -0800, VDR User wrote: > I applied this patch to the 4.8.4 kernel driver (that I'm currently > running) and it caused nothing but "frontend 0/0 timed out while > tuning". Is there another patch that should be used in conjunction > with this? If not, this patch

Re: [PATCH 2/3] Staging: media: radio-bcm2048: Fix alignment issues

On Wed, Oct 19, 2016 at 07:17:12PM +0200, Jean-Baptiste Abbadie wrote: > Signed-off-by: Jean-Baptiste Abbadie > --- > drivers/staging/media/bcm2048/radio-bcm2048.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: [PATCH v2 02/31] cinergyT2-core: don't do DMA on stack

On Tue, Oct 11, 2016 at 07:09:17AM -0300, Mauro Carvalho Chehab wrote: > --- a/drivers/media/usb/dvb-usb/cinergyT2-core.c > +++ b/drivers/media/usb/dvb-usb/cinergyT2-core.c > @@ -41,6 +41,8 @@ DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr); > > struct cinergyt2_state { > u8 rc_counter; > +

Re: [PATCH v2 02/31] cinergyT2-core: don't do DMA on stack

On Tue, Oct 11, 2016 at 07:09:17AM -0300, Mauro Carvalho Chehab wrote: > --- a/drivers/media/usb/dvb-usb/cinergyT2-core.c > +++ b/drivers/media/usb/dvb-usb/cinergyT2-core.c > @@ -41,6 +41,8 @@ DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr); > > struct cinergyt2_state { > u8 rc_counter; > +

Re: [PATCH v2 02/31] cinergyT2-core: don't do DMA on stack

On Tue, Oct 11, 2016 at 07:09:17AM -0300, Mauro Carvalho Chehab wrote: > --- a/drivers/media/usb/dvb-usb/cinergyT2-core.c > +++ b/drivers/media/usb/dvb-usb/cinergyT2-core.c > @@ -41,6 +41,8 @@ DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr); > > struct cinergyt2_state { > u8 rc_counter; > +

Re: Problem with VMAP_STACK=y

On Wed, Oct 05, 2016 at 06:04:50AM -0300, Mauro Carvalho Chehab wrote: > static int cinergyt2_frontend_attach(struct dvb_usb_adapter *adap) > { > - char query[] = { CINERGYT2_EP1_GET_FIRMWARE_VERSION }; > - char state[3]; > + struct dvb_usb_device *d = adap->dev; > + struct

Re: Problem with VMAP_STACK=y

On Wed, Oct 05, 2016 at 06:04:50AM -0300, Mauro Carvalho Chehab wrote: > static int cinergyt2_frontend_attach(struct dvb_usb_adapter *adap) > { > - char query[] = { CINERGYT2_EP1_GET_FIRMWARE_VERSION }; > - char state[3]; > + struct dvb_usb_device *d = adap->dev; > + struct

Re: Problem with VMAP_STACK=y

On Wed, Oct 05, 2016 at 06:04:50AM -0300, Mauro Carvalho Chehab wrote: > static int cinergyt2_frontend_attach(struct dvb_usb_adapter *adap) > { > - char query[] = { CINERGYT2_EP1_GET_FIRMWARE_VERSION }; > - char state[3]; > + struct dvb_usb_device *d = adap->dev; > + struct

Re: Cherryview wake up events

On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote: > David (CC'd) is working on getting the Dollar Cove PMIC driver > upstreamed to the mainline kernel. May I ask when to expect a patch? I'm ready if you have something to test, even if it's not in shape for mainline yet. Thanks,

Re: Cherryview wake up events

On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote: > David (CC'd) is working on getting the Dollar Cove PMIC driver > upstreamed to the mainline kernel. May I ask when to expect a patch? I'm ready if you have something to test, even if it's not in shape for mainline yet. Thanks,

Re: Cherryview wake up events

On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote: > On Wed, Sep 21, 2016 at 11:16:35AM +0200, Johannes Stezenbach wrote: > > There is an ADBG ("TI_DCOVE") in PMI2._STA, so Dollar Cove > > sounds like a good guess. > > David (CC'd) is working on gett

Re: Cherryview wake up events

On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote: > On Wed, Sep 21, 2016 at 11:16:35AM +0200, Johannes Stezenbach wrote: > > There is an ADBG ("TI_DCOVE") in PMI2._STA, so Dollar Cove > > sounds like a good guess. > > David (CC'd) is working on gett

Re: Cherryview wake up events

On Wed, Sep 21, 2016 at 12:06:14PM +0300, Mika Westerberg wrote: > On Tue, Sep 20, 2016 at 11:11:53PM +0200, Johannes Stezenbach wrote: > > Or it is because the PNP0C40 device depends on GpioInt from PMIC > > which isn't available... > > > > Method (_CRS,

Re: Cherryview wake up events

On Wed, Sep 21, 2016 at 12:06:14PM +0300, Mika Westerberg wrote: > On Tue, Sep 20, 2016 at 11:11:53PM +0200, Johannes Stezenbach wrote: > > Or it is because the PNP0C40 device depends on GpioInt from PMIC > > which isn't available... > > > > Method (_CRS,

  1   2   3   4   5   6   7   8   9   10   >