[U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
Hi, I am working on a board (AMOS820 from Via) based on the mx6qsabrelite. The BSP provided by the manufacturer is quite old. I managed to port it from Freescale uboot-imx rel_imx_3.0.35_4.1.0 to u-boot mainline, and basically the latest issue I have is the cpu frequency. The kernel I use is the rel_imx_3.0.35_4.1.0 as well (same tag name) With the old u-boot, it runs at 1Ghz because the BSP explicitly has a call to clk_config(CONFIG_REF_CLK_FREQ, 1000, CPU_CLK); With the new u-boot, it runs at default freq which is 800Mhz (at least, what I guess from the Bogomips because no other log says it) I have attempted to pass "arm_freq=1000" to the boot args but that does not change anything. My concern is that clk_config does not seem to be available anymore, there is get_mcu_main_clk but no set routine. I wonder if it is intentional, I could write a set routine but I wonder if it could be accepted as a patch. What it your advice about it ? Regards Thierry ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
Hi Thierry, On 18/03/2014 12:28, tbul...@free.fr wrote: > > > Hi, > > I am working on a board (AMOS820 from Via) based on the mx6qsabrelite. > > The BSP provided by the manufacturer is quite old. > I managed to port it from Freescale uboot-imx rel_imx_3.0.35_4.1.0 to u-boot > mainline, and basically the latest issue I have is the cpu frequency. > > The kernel I use is the rel_imx_3.0.35_4.1.0 as well (same tag name) > > With the old u-boot, it runs at 1Ghz because the BSP explicitly has a call to > > clk_config(CONFIG_REF_CLK_FREQ, 1000, CPU_CLK); > > With the new u-boot, it runs at default freq which is 800Mhz (at least, what I > guess from the Bogomips because no other log says it) It is can taken as reference, but checking the BogoMIPS is not the right way to proof it. You should take a look at the CCM registers when Linux is running ( CCM_ANALOG_PLL_ARM). > I have attempted to pass "arm_freq=1000" to the boot args but that does not > change anything. Well, this is a kernel issue, and related to an ancient version. > > My concern is that clk_config does not seem to be available anymore, there is > get_mcu_main_clk but no set routine. It was never available in mainline. > I wonder if it is intentional, I could write a set routine but I wonder if it > could be accepted as a patch. Why not ? All patches are discussed here and if it makes sense to merge it, it will be merged. Best regards, Stefano Babic -- = DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de = ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
Le 18/03/2014 13:34, Stefano Babic a écrit : Hi Thierry, On 18/03/2014 12:28, tbul...@free.fr wrote: Hi, I am working on a board (AMOS820 from Via) based on the mx6qsabrelite. The BSP provided by the manufacturer is quite old. I managed to port it from Freescale uboot-imx rel_imx_3.0.35_4.1.0 to u-boot mainline, and basically the latest issue I have is the cpu frequency. The kernel I use is the rel_imx_3.0.35_4.1.0 as well (same tag name) With the old u-boot, it runs at 1Ghz because the BSP explicitly has a call to clk_config(CONFIG_REF_CLK_FREQ, 1000, CPU_CLK); With the new u-boot, it runs at default freq which is 800Mhz (at least, what I guess from the Bogomips because no other log says it) It is can taken as reference, but checking the BogoMIPS is not the right way to proof it. You should take a look at the CCM registers when Linux is running ( CCM_ANALOG_PLL_ARM). I have attempted to pass "arm_freq=1000" to the boot args but that does not change anything. Well, this is a kernel issue, and related to an ancient version. My concern is that clk_config does not seem to be available anymore, there is get_mcu_main_clk but no set routine. It was never available in mainline. I wonder if it is intentional, I could write a set routine but I wonder if it could be accepted as a patch. Why not ? All patches are discussed here and if it makes sense to merge it, it will be merged. Hi Stefano, many thanks for your advice, It is now running at 1Ghz. I still have a couple of issues that prevent me to submit a patch as is: 1) The kernel (old, I know) I am using does not like that PCIe to have been formerly probed by u-boot. It hangs at probing if so. Thus I have to patch my kernel, or add an environment variable to not initialize PCIe when set, in order to keep compatible with old kernels. For now, in order to boot, I have temporary disabled PCIe support in U-boot. 2) The splashscreen (loaded at 1000) disappears when loading the kernel Would you have any idea or hints about it ? Best Regards Thierry Best regards, Stefano Babic ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
Hi Thierry, On 03/21/2014 11:47 AM, Thierry Bultel wrote: Le 18/03/2014 13:34, Stefano Babic a écrit : Hi Thierry, >> On 18/03/2014 12:28, tbul...@free.fr wrote: Hi, I am working on a board (AMOS820 from Via) based on the mx6qsabrelite. The BSP provided by the manufacturer is quite old. I managed to port it from Freescale uboot-imx rel_imx_3.0.35_4.1.0 to u-boot mainline, and basically the latest issue I have is the cpu >>> frequency. > > It is now running at 1Ghz. I still have a couple of issues that prevent me to submit a patch as is: 1) The kernel (old, I know) I am using does not like that PCIe to have been formerly probed by u-boot. It hangs at probing if so. > We haven't had any trouble with our boundary-imx_3.0.35_4.1.0 branch (which is based on rel_imx_3.0.35_4.1.0): https://github.com/boundarydevices/linux-imx6/tree/boundary-imx_3.0.35_4.1.0 You might give that a pin and see if it works for you. Troy did make some modifications to PCIe in that tree. Thus I have to patch my kernel, or add an environment variable to not initialize PCIe when set, in order to keep compatible with old kernels. > For now, in order to boot, I have temporary disabled PCIe support > in U-boot. Thanks for the ping. Marek, I didn't catch that you had enabled PCIE by default. Since there aren't any peripherals which depend on this, and even the PCIe daughter board is an extra-cost item, I'd prefer to leave this disabled and require the user to enable it specifically. AFAIK, you're the only one who's tested this. Let me know if you disagree and if you'd like me to work up the patch. Regards, Eric ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
On Friday, March 21, 2014 at 11:50:18 PM, Eric Nelson wrote: [...] > > 1) The kernel (old, I know) I am using does not like that PCIe to have > > been formerly probed by u-boot. It hangs at probing if so. > > We haven't had any trouble with our boundary-imx_3.0.35_4.1.0 branch > (which is based on rel_imx_3.0.35_4.1.0): > > https://github.com/boundarydevices/linux-imx6/tree/boundary- imx_3.0.35_4.1 > .0 > > You might give that a pin and see if it works for you. Troy did > make some modifications to PCIe in that tree. Let me remind you about that PCIe reset pin [1] again ... so, did you wire your PCIe slot's nRESET line or not on this design? Do you operate the nRESET correctly ? > > Thus I have to patch my kernel, or add an environment variable to not > > initialize PCIe when set, in order to keep compatible with old kernels. > > > > For now, in order to boot, I have temporary disabled PCIe support > > in U-boot. > > Thanks for the ping. > > Marek, I didn't catch that you had enabled PCIE by default. Maybe Stefano applied the patch which enabled the PCIe on SL ? If you want it disabled, just submit a patch, either way WFM. > Since there aren't any peripherals which depend on this, and > even the PCIe daughter board is an extra-cost item, I'd > prefer to leave this disabled and require the user to enable > it specifically. > > AFAIK, you're the only one who's tested this. Didn't you guys also test that ? But yes, I'm OK either way, feel free to send a patch. [...] [1] http://lists.denx.de/pipermail/u-boot/2014-February/172496.html Best regards, Marek Vasut ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
Thanks Marek, On 03/21/2014 06:33 PM, Marek Vasut wrote: On Friday, March 21, 2014 at 11:50:18 PM, Eric Nelson wrote: [...] 1) The kernel (old, I know) I am using does not like that PCIe to have been formerly probed by u-boot. It hangs at probing if so. We haven't had any trouble with our boundary-imx_3.0.35_4.1.0 branch (which is based on rel_imx_3.0.35_4.1.0): https://github.com/boundarydevices/linux-imx6/tree/boundary- imx_3.0.35_4.1 .0 You might give that a pin and see if it works for you. Troy did make some modifications to PCIe in that tree. Let me remind you about that PCIe reset pin [1] again ... so, did you wire your PCIe slot's nRESET line or not on this design? Do you operate the nRESET correctly ? :) It's a little late in the game for that, with lots of boards in the wild. Thus I have to patch my kernel, or add an environment variable to not initialize PCIe when set, in order to keep compatible with old kernels. > For now, in order to boot, I have temporary disabled PCIe support > in U-boot. Thanks for the ping. Marek, I didn't catch that you had enabled PCIE by default. Maybe Stefano applied the patch which enabled the PCIe on SL ? No worries. > If you want it disabled, just submit a patch, either way WFM. Since there aren't any peripherals which depend on this, and even the PCIe daughter board is an extra-cost item, I'd prefer to leave this disabled and require the user to enable it specifically. AFAIK, you're the only one who's tested this. Didn't you guys also test that ? But yes, I'm OK either way, feel > free to send a patch. Right. We did test. What I should have said was that we're not "using" this feature... Patch on the way. [...] [1] http://lists.denx.de/pipermail/u-boot/2014-February/172496.html Best regards, Marek Vasut > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
