Re: [PATCH 3/5] ARC: AXS103: DTS: Add core pll node to manage cpu frequency

2017-08-22 Thread Vineet Gupta
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote: Add core pll node (core_clk) to manage cpu frequency. core_clk represents pll itself. input_clk represents clock signal source (basically xtal) which comes to pll input. Signed-off-by: Eugeniy Paltsev ---

Re: [PATCH 1/3 v8] ARC: Set IO-coherency aperture base to LINUX_LINK_BASE

2017-08-22 Thread Vineet Gupta
On 07/12/2017 02:40 AM, Eugeniy Paltsev wrote: Most of the time we indeed use the one and only LINUX_LINK_BASE set to 0x8000_. But there might be good reasons to move the kernel to another location like 0x9z etc. And we want IOC aperture to cover entire area used by the kernel, so let's make

Specifying console via "stdout-path" property

2017-08-22 Thread Eugeniy Paltsev
Hi everyone, I got strange results when I tried to specify device to use as console via "stdout-path" property in device tree: Even If I specify device in "stdout-path" property first probed device (of those that can be used as console device) is used as console. For example:

Re: [PATCH 2/5] ARC: AXS103: Get rid of platform specific cpu clock configuration

2017-08-22 Thread Vineet Gupta
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote: We set AXS103 cpu frequency in arch/arc/plat-axs10x/axs10x.c via direct writing to pll registers for historical reasons. So get rid of AXS103 platform specific cpu clock configuration as we have driver for AXS103 core pll (AXS103 pll driver is

Re: [PATCH 3/5] ARC: AXS103: DTS: Add core pll node to manage cpu frequency

2017-08-22 Thread Vineet Gupta
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote: Add core pll node (core_clk) to manage cpu frequency. core_clk represents pll itself. input_clk represents clock signal source (basically xtal) which comes to pll input. Signed-off-by: Eugeniy Paltsev ---

Re: [PATCH 4/5] ARC: AXS103: DTS: Set cpu frequency explicitly via dts

2017-08-22 Thread Vineet Gupta
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote: Set cpu frequency explicitly via "cpu-freq" param in cpu 0 node in device tree. We add "cpu-freq" only to cpu 0 as all cpus are clocking from same clock source (same pll in our case). We override cpus node in skeleton as we don't need this change

RE: [PATCH v3 07/11] ARC: [plat-eznps] new command line argument for HW scheduler at MTM

2017-08-22 Thread Noam Camus
>From: Vineet Gupta [mailto:vineet.gup...@synopsys.com] >Sent: Monday, August 21, 2017 20:04 PM >> + >> +/* Handle an out of bounds mtm hs counter value */ static void __init >> +handle_mtm_hs_ctr_out_of_bounds_error(uint8_t val) { >> +pr_err("** The value must be in range [%d,%d]