From gregkh at linuxfoundation.org Thu Aug 3 01:32:19 2017 From: gregkh at linuxfoundation.org (Greg KH) Date: Wed, 2 Aug 2017 18:32:19 -0700 Subject: [LTSI-dev] [GIT PULL LTSI-4.9 repost] Renesas SoCs and Drivers to v4.10 In-Reply-To: <20170710132658.GA984@verge.net.au> References: <20170710131835.GA27613@verge.net.au> <20170710132658.GA984@verge.net.au> Message-ID: <20170803013219.GA3031@kroah.com> On Mon, Jul 10, 2017 at 03:26:58PM +0200, Simon Horman wrote: > [Reposting with correct tag to pull, an old revision was posted by mistake] > > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following > components to their standard as of v4.10: > > * adv7511 > * cpg > * em-sti > * gen3 > * gpio-keys > * gpio-regulator > * i2c-rcar > * i2c-sh-mobile > * intc > * irq-gic > * mach-shmobile > * pci-rcar-gen2 > * pcie-rcar > * phy-micrel > * phy-rcar-gen3-usb2 > * ravb > * rcar-can > * rcar-canfd > * rcar-dmac > * rcar-du > * rcar-fcp > * rcar-fdp1 > * rcar-rst > * rcar-snd > * renesas-soc-id > * rspi > * sh-cmt > * sh-drivers > * sh-eth > * sh-mmcif > * sh-mobile-sdhi > * sh-msiof > * sh-pfc > * sh-sci > * sh-timers > * sh-tmu > * smsc911x > * sysc > * usbhs > * vsp1 > * wm8978 > * xhci-plat > * xhci-rcar > > Limited backport of the following to provide dependencies for the above: > * drm > * fsi > * phy > * simple-scu-card > * soc-device-match > > It is a follow up to early preparatory work the main difference being > a rebase onto v4.9.36. I plan to follow-up with similar submissions > backporting Renesas SoCs and Drivers to v4.11 and v4.12. > > I have tested for build regressions on a wide range of defconfigs > on a wide range of architectures. > > There are 299 patches. > > This is based on of v4.9.36. > Earlier revisions of this work was based on v4.9.21 and v4.9.31. > > > The following changes since commit 9f86f302ec0e37e84617481c587e11c47a397e3f: > > Linux 4.9.36 (2017-07-05 14:40:44 +0200) > > are available in the git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git tags/backport/v4.9.36/snapshot-to-v4.10-flattened All now pulled and checked in, thanks! greg k-h From greg at kroah.com Thu Aug 3 01:41:57 2017 From: greg at kroah.com (Greg KH) Date: Wed, 2 Aug 2017 18:41:57 -0700 Subject: [LTSI-dev] [GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.11 In-Reply-To: <20170710133049.GB27613@verge.net.au> References: <20170710133049.GB27613@verge.net.au> Message-ID: <20170803014157.GB3031@kroah.com> On Mon, Jul 10, 2017 at 03:30:50PM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following > components to their standard as of v4.11: > > * adv7511 > * ak4642 > * clk > * cpg > * gen3 > * gpio-keys > * gpio-rcar > * gpio-regulator > * i2c-emev2 > * i2c-riic > * i2c-rcar > * i2c-sh-mobile > * ipmu-vmsa > * m25p80 > * mach-shmobile > * otsm > * pci-rcar-gen2 > * pcie-rcar > * phy-micrel > * phy-rcar-gen3-usb2 > * ravb > * rcar-can > * rcar-canfd > * rcar-dmac > * rcar-du > * rcar-fdp1 > * rcar-gyroadc > * rcar-snd > * rspi > * sata-rcar > * sh-eth > * sh-mmcif > * sh-mobile-sdhi > * sh-msiof > * sh-pfc > * sh-sci > * simple-scu-card > * st1232 > * usb3-peri > * usbhs > * vsp1 > * xhci-plat > > It is a follow up to early preparatory work the main difference being > a rebase onto v4.9.36. This is a follow-up to a similar submission > backporting Renesas SoCs and Drivers to v4.10. I plan to follow-up with > a backport to v4.12. > > I have tested for build regressions on a wide range of defconfigs > on a wide range of architectures. > > There are 255 patches. > > This is based on a similar backport to v4.10 which is in turn based on v4.9.36. > That work was posted as "[GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.10" > and is tagged as tags/backport/v4.9.31/snapshot-to-v4.10-flattened > > > The following changes since commit e629b8e80ed3dc7817ba8a92d4d8098bc5fdbe65: > > drm: bridge: add DesignWare HDMI I2S audio support (2017-07-10 14:18:08 +0200) > > are available in the git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git tags/backport/v4.9.36/snapshot-to-v4.11-flattened All now applied, thanks. greg k-h From greg at kroah.com Thu Aug 3 01:55:04 2017 From: greg at kroah.com (Greg KH) Date: Wed, 2 Aug 2017 18:55:04 -0700 Subject: [LTSI-dev] [GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.12 In-Reply-To: <20170710133333.GC27613@verge.net.au> References: <20170710133333.GC27613@verge.net.au> Message-ID: <20170803015504.GC3031@kroah.com> On Mon, Jul 10, 2017 at 03:33:34PM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following > components to their standard as of v4.12: > > It is a follow up to early preparatory work the main difference being > a rebase onto v4.9.36. This is a follow-up to a similar submission > backporting Renesas SoCs and Drivers to v4.10. I plan to follow-up with > a backport to v4.12. > > I have tested for build regressions on a wide range of defconfigs > on a wide range of architectures. > > There are 286 patches. > > This is based on a similar backports to v4.11 which is in turn based on v4.9.36. > That work was posted as "[GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.11" > and is tagged as tags/backport/v4.9.36/snapshot-to-v4.11-flattened > > > The following changes since commit 338ec844533e7bb1120f88f83a3fcc1d9618eef7: > > drm: bridge: dw-hdmi: fix building without CONFIG_OF (2017-07-10 14:51:26 +0200) > > are available in the git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git tags/backport/v4.9.36/snapshot-to-v4.12-flattened Hm, this was odd, I had to drop a number of patches in the middle here, but then got the rest to apply. Did some patches end up already in the earlier series? Anyway, all now applied, thanks. greg k-h From greg at kroah.com Thu Aug 3 01:59:37 2017 From: greg at kroah.com (Greg KH) Date: Wed, 2 Aug 2017 18:59:37 -0700 Subject: [LTSI-dev] [GIT PULL LTSI-4.9] SoCFPGA, NIOS2, and FPGA updates to v4.12 In-Reply-To: <1499700615-8738-1-git-send-email-dinguyen@kernel.org> References: <1499700615-8738-1-git-send-email-dinguyen@kernel.org> Message-ID: <20170803015937.GD3031@kroah.com> On Mon, Jul 10, 2017 at 10:30:15AM -0500, Dinh Nguyen wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following components to their standard as of v4.12: > > * edac > * fpga-manager > * gpio > * nios2 > * reset > * SoCFPGA DTS updates > * spi > > Thanks, > Dinh > > > The following changes since commit 9f86f302ec0e37e84617481c587e11c47a397e3f: > > Linux 4.9.36 (2017-07-05 14:40:44 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_updates_for_v4.9-ltsi Thanks for these, all now applied! greg k-h From horms at verge.net.au Thu Aug 3 07:45:11 2017 From: horms at verge.net.au (Simon Horman) Date: Thu, 3 Aug 2017 09:45:11 +0200 Subject: [LTSI-dev] [GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.12 In-Reply-To: <20170803015504.GC3031@kroah.com> References: <20170710133333.GC27613@verge.net.au> <20170803015504.GC3031@kroah.com> Message-ID: <20170803074511.GD19671@verge.net.au> On Wed, Aug 02, 2017 at 06:55:04PM -0700, Greg KH wrote: > On Mon, Jul 10, 2017 at 03:33:34PM +0200, Simon Horman wrote: > > Hi, > > > > This is a submission to LTSI-v4.9. > > > > This series is comprised of backports to v4.9 of the following > > components to their standard as of v4.12: > > > > It is a follow up to early preparatory work the main difference being > > a rebase onto v4.9.36. This is a follow-up to a similar submission > > backporting Renesas SoCs and Drivers to v4.10. I plan to follow-up with > > a backport to v4.12. > > > > I have tested for build regressions on a wide range of defconfigs > > on a wide range of architectures. > > > > There are 286 patches. > > > > This is based on a similar backports to v4.11 which is in turn based on v4.9.36. > > That work was posted as "[GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.11" > > and is tagged as tags/backport/v4.9.36/snapshot-to-v4.11-flattened > > > > > > The following changes since commit 338ec844533e7bb1120f88f83a3fcc1d9618eef7: > > > > drm: bridge: dw-hdmi: fix building without CONFIG_OF (2017-07-10 14:51:26 +0200) > > > > are available in the git repository at: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git tags/backport/v4.9.36/snapshot-to-v4.12-flattened > > Hm, this was odd, I had to drop a number of patches in the middle here, > but then got the rest to apply. Did some patches end up already in the > earlier series? > > Anyway, all now applied, thanks. Thanks Greg, I'll look over what you have applied. The likely explanation for the problem is that I messed things up somehow when preparing the branch for you. From fukuyasu at linuxfoundation.org Thu Aug 3 23:52:13 2017 From: fukuyasu at linuxfoundation.org (Noriaki Fukuyasu) Date: Fri, 4 Aug 2017 08:52:13 +0900 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! Message-ID: Hi everyone LTSI-4.9-RC1 is now ready for testing. http://ltsi.linuxfoundation.org/releases/ltsi-tree/4.9.40-ltsi-rc1/release-candidate I recommend to use Fuego for testing this RC1, and when you test this, please share the result with this mailing list. This process would make the kernel better for the industry usage. We are hoping to complete the testing process within August. Thank you everyone for your collaboration! regards Nori -- Noriaki Fukuyasu VP of Japan Operations The Linux Foundation Mail: fukuyasu at linuxfoundation.org Tel: +81-80-4350-1133 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sedat.dilek at gmail.com Fri Aug 11 12:18:16 2017 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Fri, 11 Aug 2017 14:18:16 +0200 Subject: [LTSI-dev] What-is-LTSI: Dead Web-Link to CELF Message-ID: [ Please CC me as I am not subscribed to this ML ] Hi, in [1] is a dead web-link in the section... "A Common LTS Kernel Tree for the CE industry The LTSI tree is an industry-managed tree based on the long term stable kernel tree, and will be published and maintained by the Consumer Electronics workgroup." ...to the CELF web-link. Please, look at this. Thanks. Regards, - Sedat - [1] http://ltsi.linuxfoundation.org/what-is-ltsi [2] http://www.linuxfoundation.org/collaborate/workgroups/celf From yoshitake.kobayashi at toshiba.co.jp Sun Aug 13 04:57:52 2017 From: yoshitake.kobayashi at toshiba.co.jp (KOBAYASHI Yoshitake) Date: Sun, 13 Aug 2017 13:57:52 +0900 Subject: [LTSI-dev] What-is-LTSI: Dead Web-Link to CELF In-Reply-To: References: Message-ID: <2b685f2f-bf82-b64d-bf4a-7cfdc2de349b@toshiba.co.jp> Hi Sedat, Thanks for reporting the issue. I think the link [2] was moved to the folowing place. https://www.linuxfoundation.org/projects/core-embedded-linux Hi LTSI team> Could you fix it? Best regards, Yoshi On 2017/08/11 21:18, Sedat Dilek wrote: > [ Please CC me as I am not subscribed to this ML ] > > Hi, > > in [1] is a dead web-link in the section... > > "A Common LTS Kernel Tree for the CE industry > > The LTSI tree is an industry-managed tree based on the long term > stable kernel tree, and will be published and maintained by the > Consumer Electronics workgroup." > > ...to the CELF web-link. > > Please, look at this. > > Thanks. > > Regards, > - Sedat - > > [1] http://ltsi.linuxfoundation.org/what-is-ltsi > [2] http://www.linuxfoundation.org/collaborate/workgroups/celf > _______________________________________________ > LTSI-dev mailing list > LTSI-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ltsi-dev > > From yoshihiro.shimoda.uh at renesas.com Wed Aug 23 08:51:20 2017 From: yoshihiro.shimoda.uh at renesas.com (Yoshihiro Shimoda) Date: Wed, 23 Aug 2017 08:51:20 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: Hi, > From: Noriaki Fukuyasu > Sent: Friday, August 4, 2017 8:52 AM > > Hi everyone > > LTSI-4.9-RC1 is now ready for testing. > http://ltsi.linuxfoundation.org/releases/ltsi-tree/4.9.40-ltsi-rc1/release-candidate > > I recommend to use Fuego for testing this RC1, and when you test this, please share the result with this mailing list. This process would make the kernel better for the industry usage. Our team tested this RC1 using Fuego 1.0 (sorry, we have trouble when we use Fuego 1.1. So, we used Fuego 1.0) on R-Car H3 Salvator-X. And, I wrote the result in the end of this email as csv format. Also, our team found some issues (the board cannot resume well) and the following patches can resolve it. Would you do cherry-pick them? Or, should I send the patches like general Linux development role? :) 5095cb8 usb: of: add functions to bind a companion controller d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected in system resume 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() c567fb3 clk: cs2000: add Suspend/Resume feature Best regards, Yoshihiro Shimoda --- No.,Test item,Remarks,Status 1,Benchmark.aim7,Failure if executed bench processing step,Success 2,Benchmark.blobsallad,Build failed,Failure 3,Benchmark.bonnie,,Success 4,Benchmark.cyclictest,,Success 5,Benchmark.dbench,,Success 6,Benchmark.Dhrystone,,Success 7,Benchmark.ebizzy,,Success 8,Benchmark.ffsb,Build failed,Failure 9,Benchmark.fio,,Success 10,Benchmark.GLMark,Build failed,Failure 11,Benchmark.gtkperf,Ditto,Failure 12,Benchmark.hackbench,,Success 13,Benchmark.himeno,,Success 14,Benchmark.Interbench,Build failed,Failure 15,Benchmark.IOzone,Ditto,Failure 16,Benchmark.iperf,Ditto,Failure 17,Benchmark.Java,Ditto,Failure 18,Benchmark.linpack,Failure if executed bench processing step,Success 19,Benchmark.lmbench2,Hang up when executed,Aborted 20,Benchmark.nbench_byte,Hang up when executed,Aborted 21,Benchmark.netperf,Build failed,Failure 22,Benchmark.netpipe,No such file patch,Failure 23,Benchmark.OpenSSL,Build failed,Failure 24,Benchmark.reboot,Failure if executed bench processing step,Success 25,Benchmark.signaltest,Ditto,Success 26,Benchmark.Stream,Ditto,Success 27,Benchmark.tiobench,Build failed,Failure 28,Benchmark.Whetstone,Ditto,Failure 29,Benchmark.x11perf,Ditto,Failure No.,Test item,Remarks,Status 1,Functional.aiostress,,Success 2,Functional.arch_timer,Need to change test specification,Success 3,Functional.bc,,Success 4,Functional.bzip2,,Success 5,Functional.cmt,Test case failed,Failure 6,Functional.crashme,,Success 7,Functional.expat,Build failed,Failure 8,Functional.fontconfig,,Success 9,Functional.ft2demos,Build failed,Failure 10,Functional.glib,Ditto,Failure 11,Functional.hello_world,,Success 12,Functional.ipv6connect,,Success 13,Functional.jpeg,,Success 14,Functional.libpng,Build failed,Failure 15,Functional.linus_stress,,Success 16,Functional.LTP.Devices,Build failed,Failure 17,Functional.LTP.Filesystem,Build failed,Failure 18,Functional.LTP.Open_Posix,Build failed,Failure 19,Functional.netperf,3/5 failed,Failure 20,Functional.OpenSSL,Hang up when executed,Aborted 21,Functional.pi_tests,,Success 22,Functional.posixtestsuite,,Success 23,Functional.rmaptest,,Success 24,Functional.scifab,Need to change test specification,Success 25,Functional.scrashme,Build failed,Failure 26,Functional.sdhi_0,Need to change test specification,Success 27,Functional.stress,,Success 28,Functional.synctest,,Success 29,Functional.zlib,,Success From geert at linux-m68k.org Wed Aug 23 10:11:25 2017 From: geert at linux-m68k.org (Geert Uytterhoeven) Date: Wed, 23 Aug 2017 12:11:25 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: Hi Fukuyasu-san, Greg, On Fri, Aug 4, 2017 at 1:52 AM, Noriaki Fukuyasu wrote: > LTSI-4.9-RC1 is now ready for testing. > http://ltsi.linuxfoundation.org/releases/ltsi-tree/4.9.40-ltsi-rc1/release-candidate Thank you for this first release candidate! Are there any plans to provide LTSI trees as git trees instead of series of patches? This would make LTSI work fit much nicer into the normal Linux kernel development workflow, and may improve the collaboration between upstream and LTSI work. A while ago, someone pointed me to the included script to generate a git tree, so finally I gave it a try. The README says: | The tree can be exported as a git tree, based on the kernel.org upstream | release described in the file KERNEL_VERSION. To do this run the | scripts/generate_git script. For more details on the environment | variables this script expects and how it works, please see the built in | help in the script by running: | scripts/generate_git --help Unfortunately that didn't help much: | $ scripts/generate_git --help | Usage: generate_git [--help | -a] | If no options are specified the script assumes no LTSI branch has been created | [--help] Shows usage information | [-a] Auto resume after last applied patch (skipping branch creation) | $ [...] Working, finally, and patches sent! Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From geert+renesas at glider.be Wed Aug 23 10:10:21 2017 From: geert+renesas at glider.be (Geert Uytterhoeven) Date: Wed, 23 Aug 2017 12:10:21 +0200 Subject: [LTSI-dev] [PATCH ltsi-kernel 1/2] generate_git: Fix check for existence of series file Message-ID: <1503483022-6452-1-git-send-email-geert+renesas@glider.be> $SERIES always contains at least the string "/series", so the check for a zero-length string never triggers. To fix this, check for the existence of the file instead. Signed-off-by: Geert Uytterhoeven --- scripts/generate_git | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/generate_git b/scripts/generate_git index 1eb4462bca67f0cb..248939a5af437257 100755 --- a/scripts/generate_git +++ b/scripts/generate_git @@ -26,7 +26,7 @@ fi DIR=`dirname $0 |sed 's/scripts$//'` SERIES=$DIR/series -if [ -z "$SERIES" ]; then +if [ ! -f "$SERIES" ]; then echo Cant find series file at $SERIES exit 1 fi -- 2.7.4 From geert+renesas at glider.be Wed Aug 23 10:10:22 2017 From: geert+renesas at glider.be (Geert Uytterhoeven) Date: Wed, 23 Aug 2017 12:10:22 +0200 Subject: [LTSI-dev] [PATCH ltsi-kernel 2/2] README: Clarify where to run the generate_git script from In-Reply-To: <1503483022-6452-1-git-send-email-geert+renesas@glider.be> References: <1503483022-6452-1-git-send-email-geert+renesas@glider.be> Message-ID: <1503483022-6452-2-git-send-email-geert+renesas@glider.be> Just running the script from the current directory doesn't give a clue: Cant find series file at /series Signed-off-by: Geert Uytterhoeven --- README | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README b/README index 00ea32badc0623e4..f6afc7f236517ded 100644 --- a/README +++ b/README @@ -62,9 +62,10 @@ Git Tree The tree can be exported as a git tree, based on the kernel.org upstream release described in the file KERNEL_VERSION. To do this run the -scripts/generate_git script. For more details on the environment -variables this script expects and how it works, please see the built in -help in the script by running: +scripts/generate_git script from a git repository that already contains +that version. For more details on the environment variables this script +expects and how it works, please see the built in help in the script by +running: scripts/generate_git --help -- 2.7.4 From geert at linux-m68k.org Fri Aug 25 08:23:11 2017 From: geert at linux-m68k.org (Geert Uytterhoeven) Date: Fri, 25 Aug 2017 10:23:11 +0200 Subject: [LTSI-dev] [[PATCH]] Revert "leds: handle suspend/resume in heartbeat trigger" In-Reply-To: <20170823193419.GA7965@amd> References: <1497321560-46817-1-git-send-email-bo.zhang@nxp.com> <20170823193419.GA7965@amd> Message-ID: On Wed, Aug 23, 2017 at 9:34 PM, Pavel Machek wrote: >> On Tue, Jun 13, 2017 at 4:39 AM, Zhang Bo wrote: >> > This reverts commit 5ab92a7cb82c66bf30685583a38a18538e3807db. >> > >> > System cannot enter suspend mode because of heartbeat led trigger. >> > In autosleep_wq, try_to_suspend function will try to enter suspend >> > mode in specific period. it will get wakeup_count then call pm_notifier >> > chain callback function and freeze processes. >> > Heartbeat_pm_notifier is called and it call led_trigger_unregister to >> > change the trigger of led device to none. It will send uevent message >> > and the wakeup source count changed. As wakeup_count changed, suspend >> > will abort. >> > >> > Signed-off-by: Zhang Bo >> >> While investigating an heartbeat LED issue in v4.9.40-ltsi, I stumpled on this >> revert (commit 436c4c45b5b9562b ("Revert "leds: handle suspend/resume in >> heartbeat trigger"") in v4.12-rc6), which was not backported to v4.9 (yet). >> >> Interestingly, while running v4.9.x on r8a7791/koelsch with an LED configured >> for heartbeat, I can actually suspend the system using s2ram. >> However, after system resume the heartbeat LED no longer flashes. >> /sys/class/leds/LED6/trigger shows the trigger is still "none", and thus >> wasn't restored to "heartbeat" by the notifier. >> There's no "could not re-register heartbeat trigger" message printed. >> >> Backporting the revert fixes this. > > You have my Acked-by: if you want to submit this to some -stable > kernels... Thank you! Greg: Can you please queue 436c4c45b5b9562b ("Revert "leds: handle suspend/resume in heartbeat trigger"") for v4.9.x or v4.9-ltsi? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From greg at kroah.com Sun Aug 27 12:46:36 2017 From: greg at kroah.com (Greg KH) Date: Sun, 27 Aug 2017 14:46:36 +0200 Subject: [LTSI-dev] [[PATCH]] Revert "leds: handle suspend/resume in heartbeat trigger" In-Reply-To: References: <1497321560-46817-1-git-send-email-bo.zhang@nxp.com> <20170823193419.GA7965@amd> Message-ID: <20170827124636.GA2038@kroah.com> On Fri, Aug 25, 2017 at 10:23:11AM +0200, Geert Uytterhoeven wrote: > On Wed, Aug 23, 2017 at 9:34 PM, Pavel Machek wrote: > >> On Tue, Jun 13, 2017 at 4:39 AM, Zhang Bo wrote: > >> > This reverts commit 5ab92a7cb82c66bf30685583a38a18538e3807db. > >> > > >> > System cannot enter suspend mode because of heartbeat led trigger. > >> > In autosleep_wq, try_to_suspend function will try to enter suspend > >> > mode in specific period. it will get wakeup_count then call pm_notifier > >> > chain callback function and freeze processes. > >> > Heartbeat_pm_notifier is called and it call led_trigger_unregister to > >> > change the trigger of led device to none. It will send uevent message > >> > and the wakeup source count changed. As wakeup_count changed, suspend > >> > will abort. > >> > > >> > Signed-off-by: Zhang Bo > >> > >> While investigating an heartbeat LED issue in v4.9.40-ltsi, I stumpled on this > >> revert (commit 436c4c45b5b9562b ("Revert "leds: handle suspend/resume in > >> heartbeat trigger"") in v4.12-rc6), which was not backported to v4.9 (yet). > >> > >> Interestingly, while running v4.9.x on r8a7791/koelsch with an LED configured > >> for heartbeat, I can actually suspend the system using s2ram. > >> However, after system resume the heartbeat LED no longer flashes. > >> /sys/class/leds/LED6/trigger shows the trigger is still "none", and thus > >> wasn't restored to "heartbeat" by the notifier. > >> There's no "could not re-register heartbeat trigger" message printed. > >> > >> Backporting the revert fixes this. > > > > You have my Acked-by: if you want to submit this to some -stable > > kernels... > > Thank you! > > Greg: Can you please queue 436c4c45b5b9562b ("Revert "leds: handle > suspend/resume in heartbeat trigger"") for v4.9.x or v4.9-ltsi? > Thanks! Now applied, thanks. greg k-h From khiem.nguyen.xt at renesas.com Mon Aug 28 03:42:51 2017 From: khiem.nguyen.xt at renesas.com (Khiem Nguyen) Date: Mon, 28 Aug 2017 03:42:51 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! Message-ID: Hi Greg, Simon, Cc Shimoda-san, Cc Tim, > > LTSI-4.9-RC1 is now ready for testing. > > http://ltsi.linuxfoundation.org/releases/ltsi-tree/4.9.40-ltsi-rc1/rel > > ease-candidate > > > > I recommend to use Fuego for testing this RC1, and when you test this, please > share the result with this mailing list. This process would make the kernel better > for the industry usage. > > Our team tested this RC1 using Fuego 1.0 (sorry, we have trouble when we use > Fuego 1.1. > So, we used Fuego 1.0) on R-Car H3 Salvator-X. Latest Fuego has not officially supported R-Car Gen3 boards (Salvator-X or Starter Kit) yet. Therefore, we have added board support locally for testing LTSI 4.9 RC1. There are other issues about test scripts in Fuego, so that some test cases could not be run successfully. We have also fixed the issues. We will send out the patches to fix test cases as well as adding new boards to Fuego. i.e after Fuego 1.2 is released in coming weeks. > And, I wrote the result in the end of this email as csv format. > > Also, our team found some issues (the board cannot resume well) and the > following patches can resolve it. > Would you do cherry-pick them? > Or, should I send the patches like general Linux development role? :) We did perform LTP test, BSP drivers test with Fuego. 1. LTP test (based on latest version, 20170516) has been executed. The test result shows no big issues on LTSI 4.9 RC1. I also attached the result for reference. 2. BSP drivers' test has been executed based on the test cases in github [1] i.e LED, RCAR-GPIO, I2C, ETHERNET, SCIF/HSCIF, Display-Unit, SDHI, SATA, USB2, USB3, RCAR-SOUND, RCAR-THERMAL, DMAE. [1] https://github.com/Jinzai-solution/SALVATOR_SHELL.git We did compare the BSP test results of LTSI 4.9 RC1 and upstream v4.12. And we found some regressions in RC1 test result due to lacking some patches. e.g some failed cases in USB, RCAR-SOUND, RCAR-THERMAL, Hence, we would like to backport more patches from v4.11 and v4.12 to fix the failed cases. > 5095cb8 usb: of: add functions to bind a companion controller > d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected in system > resume > 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in > usb_add_hcd() > d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in > usb_add_hcd() > c567fb3 clk: cs2000: add Suspend/Resume feature There are more patches (from kernel v4.12) are needed. 1/ Add the rcar-thermal driver from v4.12. 75f78d6 thermal: rcar_gen3_thermal: add suspend and resume support cc4d072 thermal: rcar_gen3_thermal: store device match data in private structure 7d4b269 thermal: rcar_gen3_thermal: enable hardware interrupts for trip points 97dad1f thermal: rcar_gen3_thermal: record and check number of TSCs found d51546c thermal: rcar_gen3_thermal: check that TSC exists before memory allocation 100cfbc thermal: rcar_gen3_thermal: remove unneeded mutex 78aefd2 thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 564e73d thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver Hi Simon, About above patches, could you check the patches and send the merging request to Greg at once ? > --- > No.,Test item,Remarks,Status > 1,Benchmark.aim7,Failure if executed bench processing step,Success > 2,Benchmark.blobsallad,Build failed,Failure 3,Benchmark.bonnie,,Success > 4,Benchmark.cyclictest,,Success 5,Benchmark.dbench,,Success > 6,Benchmark.Dhrystone,,Success 7,Benchmark.ebizzy,,Success > 8,Benchmark.ffsb,Build failed,Failure 9,Benchmark.fio,,Success > 10,Benchmark.GLMark,Build failed,Failure 11,Benchmark.gtkperf,Ditto,Failure > 12,Benchmark.hackbench,,Success > 13,Benchmark.himeno,,Success > 14,Benchmark.Interbench,Build failed,Failure 15,Benchmark.IOzone,Ditto,Failure > 16,Benchmark.iperf,Ditto,Failure 17,Benchmark.Java,Ditto,Failure > 18,Benchmark.linpack,Failure if executed bench processing step,Success > 19,Benchmark.lmbench2,Hang up when executed,Aborted > 20,Benchmark.nbench_byte,Hang up when executed,Aborted > 21,Benchmark.netperf,Build failed,Failure 22,Benchmark.netpipe,No such file > patch,Failure 23,Benchmark.OpenSSL,Build failed,Failure > 24,Benchmark.reboot,Failure if executed bench processing step,Success > 25,Benchmark.signaltest,Ditto,Success > 26,Benchmark.Stream,Ditto,Success > 27,Benchmark.tiobench,Build failed,Failure > 28,Benchmark.Whetstone,Ditto,Failure > 29,Benchmark.x11perf,Ditto,Failure > > No.,Test item,Remarks,Status > 1,Functional.aiostress,,Success > 2,Functional.arch_timer,Need to change test specification,Success > 3,Functional.bc,,Success 4,Functional.bzip2,,Success 5,Functional.cmt,Test case > failed,Failure 6,Functional.crashme,,Success 7,Functional.expat,Build > failed,Failure 8,Functional.fontconfig,,Success 9,Functional.ft2demos,Build > failed,Failure 10,Functional.glib,Ditto,Failure 11,Functional.hello_world,,Success > 12,Functional.ipv6connect,,Success > 13,Functional.jpeg,,Success > 14,Functional.libpng,Build failed,Failure 15,Functional.linus_stress,,Success > 16,Functional.LTP.Devices,Build failed,Failure 17,Functional.LTP.Filesystem,Build > failed,Failure 18,Functional.LTP.Open_Posix,Build failed,Failure > 19,Functional.netperf,3/5 failed,Failure 20,Functional.OpenSSL,Hang up when > executed,Aborted 21,Functional.pi_tests,,Success > 22,Functional.posixtestsuite,,Success > 23,Functional.rmaptest,,Success > 24,Functional.scifab,Need to change test specification,Success > 25,Functional.scrashme,Build failed,Failure 26,Functional.sdhi_0,Need to change > test specification,Success 27,Functional.stress,,Success > 28,Functional.synctest,,Success 29,Functional.zlib,,Success Best regards, KHIEM Nguyen -------------- next part -------------- A non-text attachment was scrubbed... Name: LTSI_4.9_RC1_LTP_report.xls Type: application/vnd.ms-excel Size: 74240 bytes Desc: LTSI_4.9_RC1_LTP_report.xls URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: LTSI_4.9_RC1_BSP_tests_with_Fuego.xls Type: application/vnd.ms-excel Size: 86528 bytes Desc: LTSI_4.9_RC1_BSP_tests_with_Fuego.xls URL: From geert at linux-m68k.org Tue Aug 29 13:01:51 2017 From: geert at linux-m68k.org (Geert Uytterhoeven) Date: Tue, 29 Aug 2017 15:01:51 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: (dropping fuego) On Mon, Aug 28, 2017 at 5:42 AM, Khiem Nguyen wrote: > There are more patches (from kernel v4.12) are needed. > 1/ Add the rcar-thermal driver from v4.12. > 75f78d6 thermal: rcar_gen3_thermal: add suspend and resume support > cc4d072 thermal: rcar_gen3_thermal: store device match data in private structure > 7d4b269 thermal: rcar_gen3_thermal: enable hardware interrupts for trip points > 97dad1f thermal: rcar_gen3_thermal: record and check number of TSCs found > d51546c thermal: rcar_gen3_thermal: check that TSC exists before memory allocation > 100cfbc thermal: rcar_gen3_thermal: remove unneeded mutex > 78aefd2 thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 > 564e73d thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver Thank you, I can confirm the list above can be backported fine (in reverse order ;-) Simon: apparently you have backported the R-Car Gen3 HDMI driver (cfr. commit c5bf8562271ec97f ("drm: rcar-du: Add Gen3 HDMI encoder support"), but skipped the corresponding DTS changes? One more Renesas-specific patch I would like to nominate is 13132b3f44d36009 ("ARM: dts: armadillo800eva: Split LCD mux and gpio"). It doesn't make any difference yet, but it's better not to leave known bugs in DT unfixed if they can be exposed by a kernel upgrade. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From geert at linux-m68k.org Tue Aug 29 13:07:08 2017 From: geert at linux-m68k.org (Geert Uytterhoeven) Date: Tue, 29 Aug 2017 15:07:08 +0200 Subject: [LTSI-dev] locking/spinlock/debug: Remove spinlock lockup detection code In-Reply-To: <20170220214816.F3A2B66122D@gitolite.kernel.org> References: <20170220214816.F3A2B66122D@gitolite.kernel.org> Message-ID: Hi Greg, On Mon, Feb 20, 2017 at 10:48 PM, Linux Kernel Mailing List wrote: > Web: https://git.kernel.org/torvalds/c/bc88c10d7e6900916f5e1ba3829d66a9de92b633 > Commit: bc88c10d7e6900916f5e1ba3829d66a9de92b633 > Parent: f9af456a61ecfbef8233c5046a9e347c9b98ba05 > Refname: refs/heads/master > Author: Waiman Long > AuthorDate: Wed Feb 8 14:46:48 2017 -0500 > Committer: Ingo Molnar > CommitDate: Fri Feb 10 09:09:49 2017 +0100 > > locking/spinlock/debug: Remove spinlock lockup detection code > > The current spinlock lockup detection code can sometimes produce false > positives because of the unfairness of the locking algorithm itself. > > So the lockup detection code is now removed. Instead, we are relying > on the NMI watchdog to detect potential lockup. We won't have lockup > detection if the watchdog isn't running. > > The commented-out read-write lock lockup detection code are also > removed. > > Signed-off-by: Waiman Long > Signed-off-by: Peter Zijlstra (Intel) > Cc: Andrew Morton > Cc: Linus Torvalds > Cc: Paul E. McKenney > Cc: Peter Zijlstra > Cc: Sasha Levin > Cc: Thomas Gleixner > Link: http://lkml.kernel.org/r/1486583208-11038-1-git-send-email-longman at redhat.com > Signed-off-by: Ingo Molnar Can you please backport this commit to v4.9.x and/or ltsi? It fixes the following issue in 4.9.40-ltsi on r8a7740/armadillo: BUG: spinlock lockup suspected on CPU#0, swapper/1 lock: lcdc0_device+0xa0/0x258, .magic: 00000000, .owner: /-1, .owner_cpu: 0 CPU: 0 PID: 1 Comm: swapper Not tainted 4.9.40-ltsi-armadillo-00939-gfc8b396897fd0712 #36 Hardware name: Generic R8A7740 (Flattened Device Tree) [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (do_raw_spin_lock+0xd4/0x118) [] (do_raw_spin_lock) from [] (dev_pm_get_subsys_data+0x2c/0x9c) [] (dev_pm_get_subsys_data) from [] (genpd_add_device+0x38/0x1b4) [] (genpd_add_device) from [] (of_genpd_add_device+0x38/0x50) [] (of_genpd_add_device) from [] (board_staging_register_device+0xb0/0xe8) [] (board_staging_register_device) from [] (board_staging_register_devices+0x24/0x2c) [] (board_staging_register_devices) from [] (runtime_board_check+0x2c/0x40) [] (runtime_board_check) from [] (do_one_initcall+0xac/0x154) [] (do_one_initcall) from [] (kernel_init_freeable+0x104/0x1c4) [] (kernel_init_freeable) from [] (kernel_init+0x8/0x10c) [] (kernel_init) from [] (ret_from_fork+0x14/0x24) Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From horms at verge.net.au Tue Aug 29 14:43:54 2017 From: horms at verge.net.au (Simon Horman) Date: Tue, 29 Aug 2017 16:43:54 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: <20170829144351.GA14184@verge.net.au> On Tue, Aug 29, 2017 at 03:01:51PM +0200, Geert Uytterhoeven wrote: > (dropping fuego) > > On Mon, Aug 28, 2017 at 5:42 AM, Khiem Nguyen > wrote: > > There are more patches (from kernel v4.12) are needed. > > 1/ Add the rcar-thermal driver from v4.12. > > 75f78d6 thermal: rcar_gen3_thermal: add suspend and resume support > > cc4d072 thermal: rcar_gen3_thermal: store device match data in private structure > > 7d4b269 thermal: rcar_gen3_thermal: enable hardware interrupts for trip points > > 97dad1f thermal: rcar_gen3_thermal: record and check number of TSCs found > > d51546c thermal: rcar_gen3_thermal: check that TSC exists before memory allocation > > 100cfbc thermal: rcar_gen3_thermal: remove unneeded mutex > > 78aefd2 thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 > > 564e73d thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver > > Thank you, I can confirm the list above can be backported fine > (in reverse order ;-) Confirmed. I also backported: b022e9b9d0e6 ("thermal: rcar_gen3_thermal: Document the R-Car Gen3") > Simon: apparently you have backported the R-Car Gen3 HDMI driver (cfr. > commit c5bf8562271ec97f ("drm: rcar-du: Add Gen3 HDMI encoder support"), > but skipped the corresponding DTS changes? > > One more Renesas-specific patch I would like to nominate is > 13132b3f44d36009 ("ARM: dts: armadillo800eva: Split LCD mux and gpio"). > It doesn't make any difference yet, but it's better not to leave known > bugs in DT > unfixed if they can be exposed by a kernel upgrade. Thanks, I'll look into the above ASAP. From horms at verge.net.au Tue Aug 29 14:52:51 2017 From: horms at verge.net.au (Simon Horman) Date: Tue, 29 Aug 2017 16:52:51 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: <20170829144351.GA14184@verge.net.au> References: <20170829144351.GA14184@verge.net.au> Message-ID: <20170829145251.GB14184@verge.net.au> On Tue, Aug 29, 2017 at 04:43:53PM +0200, Simon Horman wrote: > On Tue, Aug 29, 2017 at 03:01:51PM +0200, Geert Uytterhoeven wrote: > > (dropping fuego) > > > > On Mon, Aug 28, 2017 at 5:42 AM, Khiem Nguyen > > wrote: > > > There are more patches (from kernel v4.12) are needed. > > > 1/ Add the rcar-thermal driver from v4.12. > > > 75f78d6 thermal: rcar_gen3_thermal: add suspend and resume support > > > cc4d072 thermal: rcar_gen3_thermal: store device match data in private structure > > > 7d4b269 thermal: rcar_gen3_thermal: enable hardware interrupts for trip points > > > 97dad1f thermal: rcar_gen3_thermal: record and check number of TSCs found > > > d51546c thermal: rcar_gen3_thermal: check that TSC exists before memory allocation > > > 100cfbc thermal: rcar_gen3_thermal: remove unneeded mutex > > > 78aefd2 thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 > > > 564e73d thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver > > > > Thank you, I can confirm the list above can be backported fine > > (in reverse order ;-) > > Confirmed. > > I also backported: > > b022e9b9d0e6 ("thermal: rcar_gen3_thermal: Document the R-Car Gen3") > > > Simon: apparently you have backported the R-Car Gen3 HDMI driver (cfr. > > commit c5bf8562271ec97f ("drm: rcar-du: Add Gen3 HDMI encoder support"), > > but skipped the corresponding DTS changes? It looks like the DTS changes in question are: 428154de8d66 arm64: dts: renesas: r8a7795-salvator-x: Enable HDMI outputs 68b0a3cde864 arm64: dts: renesas: r8a7795-salvator-x: Add DU external dot clocks 1cdfc42d0a1b arm64: dts: renesas: salvator-x: Add HDMI output connectors dee3978e96a9 arm64: dts: renesas: salvator-x: Add DU external dot clock sources 12daaf78a723 arm64: dts: renesas: r8a7795: Add HDMI encoder support These patches were accepted for v4.13, however, the scope of the backporting work was up to v4.12. > > One more Renesas-specific patch I would like to nominate is > > > > 13132b3f44d36009 ("ARM: dts: armadillo800eva: Split LCD mux and gpio"). > > It doesn't make any difference yet, but it's better not to leave known > > bugs in DT > > unfixed if they can be exposed by a kernel upgrade. The patch above was a fix for v4.12. My expectation is that it would make it into LTSI via -stable. However, on examination I don't see it in Linus's tree at all. I'll follow up on the upstream aspects of this. From geert at linux-m68k.org Tue Aug 29 15:02:03 2017 From: geert at linux-m68k.org (Geert Uytterhoeven) Date: Tue, 29 Aug 2017 17:02:03 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: <20170829145251.GB14184@verge.net.au> References: <20170829144351.GA14184@verge.net.au> <20170829145251.GB14184@verge.net.au> Message-ID: Hi Simon, On Tue, Aug 29, 2017 at 4:52 PM, Simon Horman wrote: > On Tue, Aug 29, 2017 at 04:43:53PM +0200, Simon Horman wrote: >> On Tue, Aug 29, 2017 at 03:01:51PM +0200, Geert Uytterhoeven wrote: >> > Simon: apparently you have backported the R-Car Gen3 HDMI driver (cfr. >> > commit c5bf8562271ec97f ("drm: rcar-du: Add Gen3 HDMI encoder support"), >> > but skipped the corresponding DTS changes? > > It looks like the DTS changes in question are: > > 428154de8d66 arm64: dts: renesas: r8a7795-salvator-x: Enable HDMI outputs > 68b0a3cde864 arm64: dts: renesas: r8a7795-salvator-x: Add DU external dot clocks > 1cdfc42d0a1b arm64: dts: renesas: salvator-x: Add HDMI output connectors > dee3978e96a9 arm64: dts: renesas: salvator-x: Add DU external dot clock sources > 12daaf78a723 arm64: dts: renesas: r8a7795: Add HDMI encoder support > > These patches were accepted for v4.13, however, the scope of the > backporting work was up to v4.12. IC... >> > One more Renesas-specific patch I would like to nominate is >> > >> > 13132b3f44d36009 ("ARM: dts: armadillo800eva: Split LCD mux and gpio"). >> > It doesn't make any difference yet, but it's better not to leave known >> > bugs in DT >> > unfixed if they can be exposed by a kernel upgrade. > > The patch above was a fix for v4.12. > My expectation is that it would make it into LTSI via -stable. > However, on examination I don't see it in Linus's tree at all. It's in v4.13-rc1 and later. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From horms at verge.net.au Tue Aug 29 15:09:23 2017 From: horms at verge.net.au (Simon Horman) Date: Tue, 29 Aug 2017 17:09:23 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: <20170829145251.GB14184@verge.net.au> References: <20170829144351.GA14184@verge.net.au> <20170829145251.GB14184@verge.net.au> Message-ID: <20170829150922.GC14184@verge.net.au> On Tue, Aug 29, 2017 at 04:52:51PM +0200, Simon Horman wrote: > On Tue, Aug 29, 2017 at 04:43:53PM +0200, Simon Horman wrote: > > On Tue, Aug 29, 2017 at 03:01:51PM +0200, Geert Uytterhoeven wrote: > > > (dropping fuego) > > > > > > On Mon, Aug 28, 2017 at 5:42 AM, Khiem Nguyen > > > wrote: > > > > There are more patches (from kernel v4.12) are needed. > > > > 1/ Add the rcar-thermal driver from v4.12. > > > > 75f78d6 thermal: rcar_gen3_thermal: add suspend and resume support > > > > cc4d072 thermal: rcar_gen3_thermal: store device match data in private structure > > > > 7d4b269 thermal: rcar_gen3_thermal: enable hardware interrupts for trip points > > > > 97dad1f thermal: rcar_gen3_thermal: record and check number of TSCs found > > > > d51546c thermal: rcar_gen3_thermal: check that TSC exists before memory allocation > > > > 100cfbc thermal: rcar_gen3_thermal: remove unneeded mutex > > > > 78aefd2 thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 > > > > 564e73d thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver > > > > > > Thank you, I can confirm the list above can be backported fine > > > (in reverse order ;-) > > > > Confirmed. > > > > I also backported: > > > > b022e9b9d0e6 ("thermal: rcar_gen3_thermal: Document the R-Car Gen3") > > > > > Simon: apparently you have backported the R-Car Gen3 HDMI driver (cfr. > > > commit c5bf8562271ec97f ("drm: rcar-du: Add Gen3 HDMI encoder support"), > > > but skipped the corresponding DTS changes? > > It looks like the DTS changes in question are: > > 428154de8d66 arm64: dts: renesas: r8a7795-salvator-x: Enable HDMI outputs > 68b0a3cde864 arm64: dts: renesas: r8a7795-salvator-x: Add DU external dot clocks > 1cdfc42d0a1b arm64: dts: renesas: salvator-x: Add HDMI output connectors > dee3978e96a9 arm64: dts: renesas: salvator-x: Add DU external dot clock sources > 12daaf78a723 arm64: dts: renesas: r8a7795: Add HDMI encoder support > > These patches were accepted for v4.13, however, the scope of the > backporting work was up to v4.12. > > > > One more Renesas-specific patch I would like to nominate is > > > > > > 13132b3f44d36009 ("ARM: dts: armadillo800eva: Split LCD mux and gpio"). > > > It doesn't make any difference yet, but it's better not to leave known > > > bugs in DT > > > unfixed if they can be exposed by a kernel upgrade. > > The patch above was a fix for v4.12. > My expectation is that it would make it into LTSI via -stable. > However, on examination I don't see it in Linus's tree at all. > > I'll follow up on the upstream aspects of this. Done. I was confused because although I submitted this as a fix for v4.12 it not added to that release, rather it appeared in v4.13. This was partly because Olof did not deem it sufficiently important to be included in v4.13. My feeling is that if we wish to backport patches from v4.13 we should consider doing so wholesale. Obviously this will not be ready in time for LTSI-4.9. But it could be made available to the BSP team and others in the renesas-backport tree. And it could be circulated on the LTSI ML. This is similar to post-LTSI release backporting that has occurred in the past. From horms at verge.net.au Tue Aug 29 19:08:53 2017 From: horms at verge.net.au (Simon Horman) Date: Tue, 29 Aug 2017 21:08:53 +0200 Subject: [LTSI-dev] [GIT PULL LTSI-4.9] Second Round of Renesas SoCs and Drivers to v4.12 Message-ID: <20170829190853.GA4714@verge.net.au> Hi, This is a submission to LTSI-v4.9. This series is comprised of a backport v4.9 of the rcar-gen3-thermal driver to its as of v4.12. This was unintentionally omitted from earlier work submitted for inclusion in LTSI-4.9. There are 9 patches. This is based on a merge of: * Earlier work posted as "[GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.12" and is tagged as tags/backport/v4.9.36/snapshot-to-v4.12-flattened * v4.9.45 It appears to apply cleanly to an ltsi-4.9 tree generated using scripts/generate_git The following changes since commit 89dcb9ecf2d34cba6cba23376651476b0273db5d: Merge tag 'v4.9.45' into backport/v4.9.45/snapshot-flattened (2017-08-29 20:34:36 +0200) are available in the git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git tags/backport/v4.9.45/snapshot2-to-v4.12-flattened for you to fetch changes up to 0d29576c55e2a72e64f36f66ab8dcd279c345942: thermal: rcar_gen3_thermal: add suspend and resume support (2017-08-29 20:35:05 +0200) ---------------------------------------------------------------- Second Round of LTSI-v4.9 Preparation for Renesas SoCs to v4.12 Base: * v4.9.45 * Backport of various components for Renesas SoCs to v4.12 Component backported in this snapshot: * rcar-gen3-thermal driver ---------------------------------------------------------------- Niklas S?derlund (7): thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 thermal: rcar_gen3_thermal: remove unneeded mutex thermal: rcar_gen3_thermal: check that TSC exists before memory allocation thermal: rcar_gen3_thermal: record and check number of TSCs found thermal: rcar_gen3_thermal: enable hardware interrupts for trip points thermal: rcar_gen3_thermal: store device match data in private structure thermal: rcar_gen3_thermal: add suspend and resume support Wolfram Sang (2): thermal: rcar_gen3_thermal: Document the R-Car Gen3 thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver .../bindings/thermal/rcar-gen3-thermal.txt | 56 +++ drivers/thermal/Kconfig | 9 + drivers/thermal/Makefile | 1 + drivers/thermal/rcar_gen3_thermal.c | 504 +++++++++++++++++++++ 4 files changed, 570 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/rcar-gen3-thermal.txt create mode 100644 drivers/thermal/rcar_gen3_thermal.c From Tim.Bird at sony.com Wed Aug 30 04:57:03 2017 From: Tim.Bird at sony.com (Bird, Timothy) Date: Wed, 30 Aug 2017 04:57:03 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: > -----Original Message----- > From: Khiem Nguyen on August 27, 2017 8:43 PM > > Our team tested this RC1 using Fuego 1.0 (sorry, we have trouble when we > use > > Fuego 1.1. > > So, we used Fuego 1.0) on R-Car H3 Salvator-X. > I would like to hear what problems were encountered with Fuego 1.1 that made it necessary to stay with 1.0. > Latest Fuego has not officially supported R-Car Gen3 boards (Salvator-X or > Starter Kit) yet. > Therefore, we have added board support locally for testing LTSI 4.9 RC1. > Previously I was hesitant to add board files to Fuego, as it required Jenkins board definitions to be present in the code repository. Under the new Fuego architecture, Fuego does not ship the board definitions in our repository, and Jenkins boards can be added and removed independently of the Fuego board definitions with a simple ftc command. Therefore, I think we can add as many board definition files as we would like (and not clutter up the Jenkins interface.) That is, Fuego users will only create the Jenkins board definitions for the boards they want to use. > There are other issues about test scripts in Fuego, so that some test cases > could not be run successfully. > We have also fixed the issues. > > We will send out the patches to fix test cases as well as adding new boards to > Fuego. > i.e after Fuego 1.2 is released in coming weeks. That's great. I look forward to hearing about the issues and seeing your fixes. I would be happy to add whatever board files you have to Fuego, to make it easier for users to work with those boards. > > > And, I wrote the result in the end of this email as csv format. > > > > Also, our team found some issues (the board cannot resume well) and the > > following patches can resolve it. > > Would you do cherry-pick them? > > Or, should I send the patches like general Linux development role? :) My preference is to have the patches in a repository that I can cherry-pick from, but also have them posted to the Fuego list so that we can discuss individual patch elements on the mailing list. Since I'm not integrating the patches from the mailing list, they don't have to be as strictly formatted as they would otherwise need to be. However, I assume you can just use something like git send-email to send to the list. The standard Linux rules for posting patches apply: please send messages in plain text, with the patch inline in the message body (and not as an attachment). > We did perform LTP test, BSP drivers test with Fuego. > 1. LTP test (based on latest version, 20170516) has been executed. > The test result shows no big issues on LTSI 4.9 RC1. > I also attached the result for reference. Thanks for posting the results spreadsheets - this is very useful to see the report style you are using, and information you wished to see. Were these generated automatically or manually? We have some new abilities in Fuego 1.2 that may be helpful: - ability to skip executing a subtest in LTP ( via a spec file entry) - ability to ignore a failure of a testcase as part of the pass criteria for a test (via a criteria.json entry) > > No.,Test item,Remarks,Status > > 1,Benchmark.aim7,Failure if executed bench processing step,Success > > 2,Benchmark.blobsallad,Build failed,Failure 3,Benchmark.bonnie,,Success > > 4,Benchmark.cyclictest,,Success 5,Benchmark.dbench,,Success > > 6,Benchmark.Dhrystone,,Success 7,Benchmark.ebizzy,,Success > > 8,Benchmark.ffsb,Build failed,Failure 9,Benchmark.fio,,Success > > 10,Benchmark.GLMark,Build failed,Failure > 11,Benchmark.gtkperf,Ditto,Failure > > 12,Benchmark.hackbench,,Success > > 13,Benchmark.himeno,,Success > > 14,Benchmark.Interbench,Build failed,Failure > 15,Benchmark.IOzone,Ditto,Failure > > 16,Benchmark.iperf,Ditto,Failure 17,Benchmark.Java,Ditto,Failure > > 18,Benchmark.linpack,Failure if executed bench processing step,Success > > 19,Benchmark.lmbench2,Hang up when executed,Aborted > > 20,Benchmark.nbench_byte,Hang up when executed,Aborted > > 21,Benchmark.netperf,Build failed,Failure 22,Benchmark.netpipe,No such > file > > patch,Failure 23,Benchmark.OpenSSL,Build failed,Failure > > 24,Benchmark.reboot,Failure if executed bench processing step,Success > > 25,Benchmark.signaltest,Ditto,Success > > 26,Benchmark.Stream,Ditto,Success > > 27,Benchmark.tiobench,Build failed,Failure > > 28,Benchmark.Whetstone,Ditto,Failure > > 29,Benchmark.x11perf,Ditto,Failure > > > > No.,Test item,Remarks,Status > > 1,Functional.aiostress,,Success > > 2,Functional.arch_timer,Need to change test specification,Success > > 3,Functional.bc,,Success 4,Functional.bzip2,,Success 5,Functional.cmt,Test > case > > failed,Failure 6,Functional.crashme,,Success 7,Functional.expat,Build > > failed,Failure 8,Functional.fontconfig,,Success 9,Functional.ft2demos,Build > > failed,Failure 10,Functional.glib,Ditto,Failure > 11,Functional.hello_world,,Success > > 12,Functional.ipv6connect,,Success > > 13,Functional.jpeg,,Success > > 14,Functional.libpng,Build failed,Failure 15,Functional.linus_stress,,Success > > 16,Functional.LTP.Devices,Build failed,Failure > 17,Functional.LTP.Filesystem,Build > > failed,Failure 18,Functional.LTP.Open_Posix,Build failed,Failure > > 19,Functional.netperf,3/5 failed,Failure 20,Functional.OpenSSL,Hang up > when > > executed,Aborted 21,Functional.pi_tests,,Success > > 22,Functional.posixtestsuite,,Success > > 23,Functional.rmaptest,,Success > > 24,Functional.scifab,Need to change test specification,Success > > 25,Functional.scrashme,Build failed,Failure 26,Functional.sdhi_0,Need to > change > > test specification,Success 27,Functional.stress,,Success > > 28,Functional.synctest,,Success 29,Functional.zlib,,Success Fuego still needs some work in the area of identifying and capturing the location of the failure (particularly build failures) and putting that into the log data. Some errors shows up in the console log, and humans have to read that to interpret the failure. After 1.2, I hope to improve this so that Fuego can 1) add Fuego phase data to test results output file (run.json), 2) parse the build portion of the log to isolate the error. This will help users avoid having to read through the console log in order to find and identify some problems. Thanks very much for the information and feedback. -- Tim From yoshihiro.shimoda.uh at renesas.com Wed Aug 30 09:36:26 2017 From: yoshihiro.shimoda.uh at renesas.com (Yoshihiro Shimoda) Date: Wed, 30 Aug 2017 09:36:26 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: Hi, > From: Bird, Timothy > Sent: Wednesday, August 30, 2017 1:57 PM > > > -----Original Message----- > > From: Khiem Nguyen on August 27, 2017 8:43 PM < snip > > > > And, I wrote the result in the end of this email as csv format. > > > > > > Also, our team found some issues (the board cannot resume well) and the > > > following patches can resolve it. > > > Would you do cherry-pick them? > > > Or, should I send the patches like general Linux development role? :) > > My preference is to have the patches in a repository that I can cherry-pick from, > but also have them posted to the Fuego list so that we can discuss individual > patch elements on the mailing list. Since I'm not integrating the patches > from the mailing list, they don't have to be as strictly formatted as they > would otherwise need to be. However, I assume you can just use something > like git send-email to send to the list. The standard Linux rules for > posting patches apply: please send messages in plain text, with the patch > inline in the message body (and not as an attachment). Thank you for the reply. I got it. Hi Simon-san, Would you submit the following patches to LTSI ML like r-car thermal? 5095cb8 usb: of: add functions to bind a companion controller d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected in system resume 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() and c567fb3 clk: cs2000: add Suspend/Resume feature Best regards, Yoshihro Shimoda From horms at verge.net.au Wed Aug 30 11:04:52 2017 From: horms at verge.net.au (Simon Horman) Date: Wed, 30 Aug 2017 13:04:52 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: <20170830110452.GC15918@verge.net.au> On Wed, Aug 30, 2017 at 09:36:26AM +0000, Yoshihiro Shimoda wrote: > Hi, > > > From: Bird, Timothy > > Sent: Wednesday, August 30, 2017 1:57 PM > > > > > -----Original Message----- > > > From: Khiem Nguyen on August 27, 2017 8:43 PM > < snip > > > > > And, I wrote the result in the end of this email as csv format. > > > > > > > > Also, our team found some issues (the board cannot resume well) and the > > > > following patches can resolve it. > > > > Would you do cherry-pick them? > > > > Or, should I send the patches like general Linux development role? :) > > > > My preference is to have the patches in a repository that I can cherry-pick from, > > but also have them posted to the Fuego list so that we can discuss individual > > patch elements on the mailing list. Since I'm not integrating the patches > > from the mailing list, they don't have to be as strictly formatted as they > > would otherwise need to be. However, I assume you can just use something > > like git send-email to send to the list. The standard Linux rules for > > posting patches apply: please send messages in plain text, with the patch > > inline in the message body (and not as an attachment). > > Thank you for the reply. I got it. > > > Hi Simon-san, > > Would you submit the following patches to LTSI ML like r-car thermal? > > 5095cb8 usb: of: add functions to bind a companion controller > d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected in system resume > 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() > d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() > > and > > c567fb3 clk: cs2000: add Suspend/Resume feature Sure, can do. I would, however, ask Greg for a bit of time to at do some comprehensive build tests as these patches touch code used by many platforms. From khiem.nguyen.xt at renesas.com Wed Aug 30 11:25:02 2017 From: khiem.nguyen.xt at renesas.com (Khiem Nguyen) Date: Wed, 30 Aug 2017 11:25:02 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: Hi Simon, Cc Shimoda-san, Greg, > Would you submit the following patches to LTSI ML like r-car thermal? > > 5095cb8 usb: of: add functions to bind a companion controller > d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected in system > resume > 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in > usb_add_hcd() > d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in > usb_add_hcd() > > and > > c567fb3 clk: cs2000: add Suspend/Resume feature I happened to recognize that we need to backport some patches for Ethernet driver in H3ULCB and M3ULCB. Previous test report showed the result after merging the patch. I updated the test result for this information. For H3ULCB, the patches have been available in kernel v4.12. 144bf6c arm64: dts: h3ulcb: enable EthernetAVB 5b9fd19 arm64: dts: h3ulcb: Fix EthernetAVB PHY timing For M3ULCB, the patches have been merged into kernel v4.13-rc1. 883fae3 arm64: dts: m3ulcb: enable EthernetAVB bdb3656 arm64: dts: m3ulcb: Fix EthernetAVB PHY timing Although the scope of backporting is up to v4.12, please also consider for the patches in v4.13-rc1. Best regards, KHIEM Nguyen -------------- next part -------------- A non-text attachment was scrubbed... Name: LTSI_4.9_RC1_BSP_tests_with_Fuego_v2.xls Type: application/vnd.ms-excel Size: 86016 bytes Desc: LTSI_4.9_RC1_BSP_tests_with_Fuego_v2.xls URL: From khiem.nguyen.xt at renesas.com Wed Aug 30 11:43:24 2017 From: khiem.nguyen.xt at renesas.com (Khiem Nguyen) Date: Wed, 30 Aug 2017 11:43:24 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: Hi Simon, > > Would you submit the following patches to LTSI ML like r-car thermal? > > > > 5095cb8 usb: of: add functions to bind a companion controller > > d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected > > in system resume > > 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in > > usb_add_hcd() > > d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in > > usb_add_hcd() > > > > and > > > > c567fb3 clk: cs2000: add Suspend/Resume feature > > I happened to recognize that we need to backport some patches for Ethernet > driver in H3ULCB and M3ULCB. > Previous test report showed the result after merging the patch. > I updated the test result for this information. > > For H3ULCB, the patches have been available in kernel v4.12. > 144bf6c arm64: dts: h3ulcb: enable EthernetAVB > 5b9fd19 arm64: dts: h3ulcb: Fix EthernetAVB PHY timing H3ULCB will need another PFC patch from v4.13-rc1. 30c078d pinctrl: sh-pfc: r8a7795: Add EtherAVB pins, groups and function > For M3ULCB, the patches have been merged into kernel v4.13-rc1. > 883fae3 arm64: dts: m3ulcb: enable EthernetAVB > bdb3656 arm64: dts: m3ulcb: Fix EthernetAVB PHY timing > > Although the scope of backporting is up to v4.12, please also consider for the > patches in v4.13-rc1. Best regards, KHIEM Nguyen From Tim.Bird at sony.com Wed Aug 30 16:13:55 2017 From: Tim.Bird at sony.com (Bird, Timothy) Date: Wed, 30 Aug 2017 16:13:55 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: > -----Original Message----- > From: Yoshihiro Shimoda on Wednesday, August 30, 2017 2:36 AM > > From: Bird, Timothy > > Sent: Wednesday, August 30, 2017 1:57 PM > > > > > -----Original Message----- > > > From: Khiem Nguyen on August 27, 2017 8:43 PM > < snip > > > > > And, I wrote the result in the end of this email as csv format. > > > > > > > > Also, our team found some issues (the board cannot resume well) and > the > > > > following patches can resolve it. > > > > Would you do cherry-pick them? > > > > Or, should I send the patches like general Linux development role? :) > > > > My preference is to have the patches in a repository that I can cherry-pick > from, > > but also have them posted to the Fuego list so that we can discuss > individual > > patch elements on the mailing list. Since I'm not integrating the patches > > from the mailing list, they don't have to be as strictly formatted as they > > would otherwise need to be. However, I assume you can just use > something > > like git send-email to send to the list. The standard Linux rules for > > posting patches apply: please send messages in plain text, with the patch > > inline in the message body (and not as an attachment). > > Thank you for the reply. I got it. Oops. I misread the original message. I thought the reference was for patches to Fuego. I shouldn't really speak for the patch contribution policies for LTSI. Sorry - please ignore what I said, with respect to LTSI patch contributions. -- Tim From horms at verge.net.au Wed Aug 30 15:00:30 2017 From: horms at verge.net.au (Simon Horman) Date: Wed, 30 Aug 2017 17:00:30 +0200 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: <20170830150030.GA29946@verge.net.au> On Wed, Aug 30, 2017 at 11:43:24AM +0000, Khiem Nguyen wrote: > Hi Simon, > > > > Would you submit the following patches to LTSI ML like r-car thermal? > > > > > > 5095cb8 usb: of: add functions to bind a companion controller > > > d4d7512 usb: host: ehci-platform: fix usb 1.1 device is not connected > > > in system resume > > > 42a58c9 usb: host: ehci-platform: set hcd->phy to avoid phy_get() in > > > usb_add_hcd() > > > d3d6ef1 usb: host: ohci-platform: set hcd->phy to avoid phy_get() in > > > usb_add_hcd() > > > > > > and > > > > > > c567fb3 clk: cs2000: add Suspend/Resume feature > > > > I happened to recognize that we need to backport some patches for Ethernet > > driver in H3ULCB and M3ULCB. > > Previous test report showed the result after merging the patch. > > I updated the test result for this information. > > > > For H3ULCB, the patches have been available in kernel v4.12. > > 144bf6c arm64: dts: h3ulcb: enable EthernetAVB The patch above was included in v4.9 and is thus present in LTSI-4.9's base. > > 5b9fd19 arm64: dts: h3ulcb: Fix EthernetAVB PHY timing The above patch has already been submitted to and accepted into LTSI-4.9. > > H3ULCB will need another PFC patch from v4.13-rc1. > 30c078d pinctrl: sh-pfc: r8a7795: Add EtherAVB pins, groups and function > > > For M3ULCB, the patches have been merged into kernel v4.13-rc1. > > 883fae3 arm64: dts: m3ulcb: enable EthernetAVB > > bdb3656 arm64: dts: m3ulcb: Fix EthernetAVB PHY timing > > > > Although the scope of backporting is up to v4.12, please also consider > > for the patches in v4.13-rc1. I am sorry but would prefer not to extend the scope of the backports beyond v4.12 at this point. From greg at kroah.com Thu Aug 31 06:03:00 2017 From: greg at kroah.com (Greg KH) Date: Thu, 31 Aug 2017 08:03:00 +0200 Subject: [LTSI-dev] locking/spinlock/debug: Remove spinlock lockup detection code In-Reply-To: References: <20170220214816.F3A2B66122D@gitolite.kernel.org> Message-ID: <20170831060300.GB7325@kroah.com> On Tue, Aug 29, 2017 at 03:07:08PM +0200, Geert Uytterhoeven wrote: > Hi Greg, > > On Mon, Feb 20, 2017 at 10:48 PM, Linux Kernel Mailing List > wrote: > > Web: https://git.kernel.org/torvalds/c/bc88c10d7e6900916f5e1ba3829d66a9de92b633 > > Commit: bc88c10d7e6900916f5e1ba3829d66a9de92b633 > > Parent: f9af456a61ecfbef8233c5046a9e347c9b98ba05 > > Refname: refs/heads/master > > Author: Waiman Long > > AuthorDate: Wed Feb 8 14:46:48 2017 -0500 > > Committer: Ingo Molnar > > CommitDate: Fri Feb 10 09:09:49 2017 +0100 > > > > locking/spinlock/debug: Remove spinlock lockup detection code > > > > The current spinlock lockup detection code can sometimes produce false > > positives because of the unfairness of the locking algorithm itself. > > > > So the lockup detection code is now removed. Instead, we are relying > > on the NMI watchdog to detect potential lockup. We won't have lockup > > detection if the watchdog isn't running. > > > > The commented-out read-write lock lockup detection code are also > > removed. > > > > Signed-off-by: Waiman Long > > Signed-off-by: Peter Zijlstra (Intel) > > Cc: Andrew Morton > > Cc: Linus Torvalds > > Cc: Paul E. McKenney > > Cc: Peter Zijlstra > > Cc: Sasha Levin > > Cc: Thomas Gleixner > > Link: http://lkml.kernel.org/r/1486583208-11038-1-git-send-email-longman at redhat.com > > Signed-off-by: Ingo Molnar > > Can you please backport this commit to v4.9.x and/or ltsi? > > It fixes the following issue in 4.9.40-ltsi on r8a7740/armadillo: > > BUG: spinlock lockup suspected on CPU#0, swapper/1 > lock: lcdc0_device+0xa0/0x258, .magic: 00000000, .owner: > /-1, .owner_cpu: 0 > CPU: 0 PID: 1 Comm: swapper Not tainted > 4.9.40-ltsi-armadillo-00939-gfc8b396897fd0712 #36 > Hardware name: Generic R8A7740 (Flattened Device Tree) > [] (unwind_backtrace) from [] (show_stack+0x10/0x14) > [] (show_stack) from [] (do_raw_spin_lock+0xd4/0x118) > [] (do_raw_spin_lock) from [] > (dev_pm_get_subsys_data+0x2c/0x9c) > [] (dev_pm_get_subsys_data) from [] > (genpd_add_device+0x38/0x1b4) > [] (genpd_add_device) from [] > (of_genpd_add_device+0x38/0x50) > [] (of_genpd_add_device) from [] > (board_staging_register_device+0xb0/0xe8) > [] (board_staging_register_device) from [] > (board_staging_register_devices+0x24/0x2c) > [] (board_staging_register_devices) from [] > (runtime_board_check+0x2c/0x40) > [] (runtime_board_check) from [] > (do_one_initcall+0xac/0x154) > [] (do_one_initcall) from [] > (kernel_init_freeable+0x104/0x1c4) > [] (kernel_init_freeable) from [] > (kernel_init+0x8/0x10c) > [] (kernel_init) from [] (ret_from_fork+0x14/0x24) > Now queud up, thanks. greg k-h From yoshihiro.shimoda.uh at renesas.com Thu Aug 31 08:42:37 2017 From: yoshihiro.shimoda.uh at renesas.com (Yoshihiro Shimoda) Date: Thu, 31 Aug 2017 08:42:37 +0000 Subject: [LTSI-dev] LTSI-4.9 RC1 is out for testing! In-Reply-To: References: Message-ID: > -----Original Message----- > From: Bird, Timothy > Sent: Thursday, August 31, 2017 1:14 AM > > > -----Original Message----- > > From: Yoshihiro Shimoda on Wednesday, August 30, 2017 2:36 AM > > > From: Bird, Timothy > > > Sent: Wednesday, August 30, 2017 1:57 PM > > > > > > > -----Original Message----- > > > > From: Khiem Nguyen on August 27, 2017 8:43 PM > > < snip > > > > > > And, I wrote the result in the end of this email as csv format. > > > > > > > > > > Also, our team found some issues (the board cannot resume well) and > > the > > > > > following patches can resolve it. > > > > > Would you do cherry-pick them? > > > > > Or, should I send the patches like general Linux development role? :) > > > > > > My preference is to have the patches in a repository that I can cherry-pick > > from, > > > but also have them posted to the Fuego list so that we can discuss > > individual > > > patch elements on the mailing list. Since I'm not integrating the patches > > > from the mailing list, they don't have to be as strictly formatted as they > > > would otherwise need to be. However, I assume you can just use > > something > > > like git send-email to send to the list. The standard Linux rules for > > > posting patches apply: please send messages in plain text, with the patch > > > inline in the message body (and not as an attachment). > > > > Thank you for the reply. I got it. > > Oops. I misread the original message. I thought the reference was for patches > to Fuego. I shouldn't really speak for the patch contribution policies for LTSI. > Sorry - please ignore what I said, with respect to LTSI patch contributions. I got it. Our team is also interesting with Fuego community's process. So, your comments are helpful to us. Best regards, Yoshihiro Shimoda > -- Tim From horms at verge.net.au Thu Aug 31 14:04:47 2017 From: horms at verge.net.au (Simon Horman) Date: Thu, 31 Aug 2017 16:04:47 +0200 Subject: [LTSI-dev] [GIT PULL LTSI-4.9] Third Round of Renesas SoCs and Drivers to v4.12 Message-ID: <20170831140447.GA24787@verge.net.au> Hi, This is a submission to LTSI-v4.9. This series is comprised of a limited backport to v4.9 of usb core, ohci-platform, ehci-platform and cs2000. These were have been suggested after examination and testing of LTSI-4.9 RC1. There are 5 patches. This is based on a merge of: * Earlier work posted as "[GIT PULL LTSI-4.9] Second Round Renesas SoCs and Drivers to v4.12" and is tagged as tags/backport/v4.9.45/snapshot2-to-v4.12-flattened * v4.9.46 It appears to apply cleanly to an ltsi-4.9 tree generated using scripts/generate_git The following changes since commit 06ce9c3fa43d22ed328b979562b16216053d031d: Merge tag 'v4.9.46' into backport/v4.9.46/snapshot-flattened (2017-08-31 12:31:10 +0200) are available in the git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git tags/backport/v4.9.46/snapshot3-to-v4.12-flattened for you to fetch changes up to ea34fab45250defe5605f8ebf4d80872e6022925: clk: cs2000: add Suspend/Resume feature (2017-08-31 12:32:25 +0200) ---------------------------------------------------------------- Third Round of LTSI-v4.9 Preparation for Renesas SoCs to v4.12 Base: * v4.9.46 * Second round of such backports Components selectively backported in this snapshot: * usb core * ohci-platform * ehci-platform * cs2000 ---------------------------------------------------------------- Khiem Nguyen (1): clk: cs2000: add Suspend/Resume feature Yoshihiro Shimoda (4): usb: of: add functions to bind a companion controller usb: host: ehci-platform: fix usb 1.1 device is not connected in system resume usb: host: ehci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() usb: host: ohci-platform: set hcd->phy to avoid phy_get() in usb_add_hcd() Documentation/devicetree/bindings/usb/generic.txt | 1 + drivers/clk/clk-cs2000-cp.c | 22 ++++++++++++++++++++++ drivers/usb/core/of.c | 23 +++++++++++++++++++++++ drivers/usb/host/ehci-platform.c | 10 ++++++++++ drivers/usb/host/ohci-platform.c | 3 +++ include/linux/usb/of.h | 5 +++++ 6 files changed, 64 insertions(+)