| Message ID | 56192135.2080608@rock-chips.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hello Yakir, Sorry for the delay but I was on holidays. On 10/10/2015 04:31 PM, Yakir Yang wrote: > Hi Javier, [snip] >>> >>>> Maybe you can email me the method the run mainline kernel on Peach >>>> Pit, so I can debug the analogix_dp driver at the same time, that would >>>> be great. >>> I wrote a little blog post explaining how to run mainline on these boards: >>> >>> http://blogs.s-osg.org/install-linux-mainline-kernel-distro-exynos-chromebooks/ >>> >>> That explains the simplest setup though so if you need a different one >>> (i.e: chain loading a non verified u-boot) or if you have any questions, >>> feel free to contact me in private and I can help you with the setup. >>> >> >> Ah, thanks, gonna to step-by-step. > > Thanks for your great material, although I meet some problems in the step-by-step > process, and failed at this way to setup mainline kernel environment on Exynos chromebooks. > > But i do find another way to install mainline kernel to Exynos Chromebook: > 1. Install any ChromeOS image into a USB media device (like dd tools) > 2. "enable_dev_usb_boot" on Exynos chromebooks which would allowed boot from USB. > 3. Flash the mainline kernel into the KERNEL-A and KERNEL-B partitions on host PC. > 4. Insert USB device into Exynos chromebooks, and press CTRL+U, boot into USB OS. Yes, as I mentioned in the blog, there are many options. In fact I also boot from a uSD instead of the eMMC since is easier for me to flash from the host machine and chain load a non-verified u-boot so I can boot non signed kernels. But thought that the most common use case would be to install it in the KERN-C and ROOT-C partitions in the eMMC. Anyways, I'm glad that you got it working. > > And it's better to enable pstore function on mainline kernel, so we can analysis the last log when > the mainline kernel crashed. After enable PSTORE_RAM in .config, we still need add ramoops node Interesting, I knew about pstore but I never used it with the Exynos Chromebooks. > into file, like: > --- a/arch/arm/boot/dts/exynos5250.dtsi > +++ b/arch/arm/boot/dts/exynos5250.dtsi > @@ -750,6 +750,15 @@ > iommu = <&sysmmu_gsc3>; > }; > > + ramoops: ramoops { > + compatible = "ramoops"; > + name = "ramoops"; > + reg = <0x41f00000 0x100000>; > + record-size = <0x20000>; > + dump-oops; > + status = "okay"; > + }; > + Are you using mainline? There isn't a "ramoops" compatible string documented in the upstream DT bindings, platform_match() would match by driver name as a fallback but I don't see code in fs/pstore/ram.c that parses the properties in your device node. I wonder how this works for you or did I missunderstand? > hdmi: hdmi { > compatible = "samsung,exynos4212-hdmi"; > reg = <0x14530000 0x70000>; > > > Aha, I have tested this series on two Exynos Chromebooks that I borrowed(Snow and Peach Pit) > with previously method (actually I believed it's a common method without broken the original > ChromeOS image). > > And I do find the crash place that make you failed at this series, here is the diff changes: > diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c > index 5f8fc11..bcbc009 100644 > --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c > +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c > @@ -1169,6 +1169,7 @@ static int analogix_dp_create_bridge(struct drm_device *drm_dev, > > dp->bridge = bridge; > > + dp->encoder->bridge = bridge; > bridge->driver_private = dp; > bridge->encoder = dp->encoder; > bridge->funcs = &analogix_dp_bridge_funcs; > --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts > +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts > @@ -151,7 +151,7 @@ > samsung,color-depth = <1>; > samsung,link-rate = <0x06>; > samsung,lane-count = <2>; > - hpd-gpio = <&gpx2 6 0>; > + hpd-gpios = <&gpx2 6 0>; > > ports { > port@0 { > > > Anyway I'm going to send the v6 series, thanks for your good idea. > Great, I'll try to test your latest series on my Peach Pi today. > - Yakir > Best regards,
Hi Javierm On 10/13/2015 05:21 PM, Javier Martinez Canillas wrote: > Hello Yakir, > > Sorry for the delay but I was on holidays. > > On 10/10/2015 04:31 PM, Yakir Yang wrote: >> Hi Javier, > [snip] > >>>>> Maybe you can email me the method the run mainline kernel on Peach >>>>> Pit, so I can debug the analogix_dp driver at the same time, that would >>>>> be great. >>>> I wrote a little blog post explaining how to run mainline on these boards: >>>> >>>> http://blogs.s-osg.org/install-linux-mainline-kernel-distro-exynos-chromebooks/ >>>> >>>> That explains the simplest setup though so if you need a different one >>>> (i.e: chain loading a non verified u-boot) or if you have any questions, >>>> feel free to contact me in private and I can help you with the setup. >>>> >>> Ah, thanks, gonna to step-by-step. >> Thanks for your great material, although I meet some problems in the step-by-step >> process, and failed at this way to setup mainline kernel environment on Exynos chromebooks. >> >> But i do find another way to install mainline kernel to Exynos Chromebook: >> 1. Install any ChromeOS image into a USB media device (like dd tools) >> 2. "enable_dev_usb_boot" on Exynos chromebooks which would allowed boot from USB. >> 3. Flash the mainline kernel into the KERNEL-A and KERNEL-B partitions on host PC. >> 4. Insert USB device into Exynos chromebooks, and press CTRL+U, boot into USB OS. > Yes, as I mentioned in the blog, there are many options. In fact I also boot from > a uSD instead of the eMMC since is easier for me to flash from the host machine > and chain load a non-verified u-boot so I can boot non signed kernels. > > But thought that the most common use case would be to install it in the KERN-C and > ROOT-C partitions in the eMMC. Anyways, I'm glad that you got it working. :-P >> And it's better to enable pstore function on mainline kernel, so we can analysis the last log when >> the mainline kernel crashed. After enable PSTORE_RAM in .config, we still need add ramoops node > Interesting, I knew about pstore but I never used it with the Exynos Chromebooks. > >> into file, like: >> --- a/arch/arm/boot/dts/exynos5250.dtsi >> +++ b/arch/arm/boot/dts/exynos5250.dtsi >> @@ -750,6 +750,15 @@ >> iommu = <&sysmmu_gsc3>; >> }; >> >> + ramoops: ramoops { >> + compatible = "ramoops"; >> + name = "ramoops"; >> + reg = <0x41f00000 0x100000>; >> + record-size = <0x20000>; >> + dump-oops; >> + status = "okay"; >> + }; >> + > Are you using mainline? There isn't a "ramoops" compatible string documented > in the upstream DT bindings, platform_match() would match by driver name as > a fallback but I don't see code in fs/pstore/ram.c that parses the properties > in your device node. I wonder how this works for you or did I missunderstand? Aha, I lost some things that I back port the pstore/ram.c from chrome v3.14 tree which driver would parsed the "ramoops" compatible. And those "ramoops" device node should be structured by bootloader in chromeos, so we won't see anything about "ramoops" in DT binding. Due to I can't upgraded the loader of Peach Pit, so I chose to structure that device manually. (detailed properties just `cat /proc/device-tree/ramoops/*`) > >> hdmi: hdmi { >> compatible = "samsung,exynos4212-hdmi"; >> reg = <0x14530000 0x70000>; >> >> >> Aha, I have tested this series on two Exynos Chromebooks that I borrowed(Snow and Peach Pit) >> with previously method (actually I believed it's a common method without broken the original >> ChromeOS image). >> >> And I do find the crash place that make you failed at this series, here is the diff changes: >> diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c >> index 5f8fc11..bcbc009 100644 >> --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c >> +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c >> @@ -1169,6 +1169,7 @@ static int analogix_dp_create_bridge(struct drm_device *drm_dev, >> >> dp->bridge = bridge; >> >> + dp->encoder->bridge = bridge; >> bridge->driver_private = dp; >> bridge->encoder = dp->encoder; >> bridge->funcs = &analogix_dp_bridge_funcs; >> --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts >> +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts >> @@ -151,7 +151,7 @@ >> samsung,color-depth = <1>; >> samsung,link-rate = <0x06>; >> samsung,lane-count = <2>; >> - hpd-gpio = <&gpx2 6 0>; >> + hpd-gpios = <&gpx2 6 0>; >> >> ports { >> port@0 { >> >> >> Anyway I'm going to send the v6 series, thanks for your good idea. >> > Great, I'll try to test your latest series on my Peach Pi today. Thanks - Yakir > >> - Yakir >> > Best regards, -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Yakir, On 10/13/2015 03:50 PM, Yakir Yang wrote: > On 10/13/2015 05:21 PM, Javier Martinez Canillas wrote: > [snip] >>> And it's better to enable pstore function on mainline kernel, so we can analysis the last log when >>> the mainline kernel crashed. After enable PSTORE_RAM in .config, we still need add ramoops node >> Interesting, I knew about pstore but I never used it with the Exynos Chromebooks. >> >>> into file, like: >>> --- a/arch/arm/boot/dts/exynos5250.dtsi >>> +++ b/arch/arm/boot/dts/exynos5250.dtsi >>> @@ -750,6 +750,15 @@ >>> iommu = <&sysmmu_gsc3>; >>> }; >>> >>> + ramoops: ramoops { >>> + compatible = "ramoops"; >>> + name = "ramoops"; >>> + reg = <0x41f00000 0x100000>; >>> + record-size = <0x20000>; >>> + dump-oops; >>> + status = "okay"; >>> + }; >>> + >> Are you using mainline? There isn't a "ramoops" compatible string documented >> in the upstream DT bindings, platform_match() would match by driver name as >> a fallback but I don't see code in fs/pstore/ram.c that parses the properties >> in your device node. I wonder how this works for you or did I missunderstand? > > Aha, I lost some things that I back port the pstore/ram.c from chrome > v3.14 tree which driver would parsed the "ramoops" compatible. > Ah, that explains it then. Best regards,
--- a/arch/arm/boot/dts/exynos5250.dtsi +++ b/arch/arm/boot/dts/exynos5250.dtsi @@ -750,6 +750,15 @@ iommu = <&sysmmu_gsc3>; }; + ramoops: ramoops { + compatible = "ramoops"; + name = "ramoops"; + reg = <0x41f00000 0x100000>; + record-size = <0x20000>; + dump-oops; + status = "okay"; + }; + hdmi: hdmi { compatible = "samsung,exynos4212-hdmi"; reg = <0x14530000 0x70000>; Aha, I have tested this series on two Exynos Chromebooks that I borrowed(Snow and Peach Pit) with previously method (actually I believed it's a common method without broken the original ChromeOS image). And I do find the crash place that make you failed at this series, here is the diff changes: diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c index 5f8fc11..bcbc009 100644 --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c @@ -1169,6 +1169,7 @@ static int analogix_dp_create_bridge(struct drm_device *drm_dev, dp->bridge = bridge; + dp->encoder->bridge = bridge; bridge->driver_private = dp; bridge->encoder = dp->encoder; bridge->funcs = &analogix_dp_bridge_funcs; --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts @@ -151,7 +151,7 @@ samsung,color-depth = <1>; samsung,link-rate = <0x06>; samsung,lane-count = <2>; - hpd-gpio = <&gpx2 6 0>; + hpd-gpios = <&gpx2 6 0>; ports { port@0 {