* [PATCH 1/9] ARC: [dts] Add clk feeding into timers to DTs [not found] <1454410739-24444-1-git-send-email-vgupta@synopsys.com> @ 2016-02-02 10:58 ` Vineet Gupta 2016-02-02 10:58 ` [PATCH 2/9] ARC: [dts] Introduce Timer bindings Vineet Gupta 1 sibling, 0 replies; 13+ messages in thread From: Vineet Gupta @ 2016-02-02 10:58 UTC (permalink / raw) To: linux-snps-arc, Alexey.Brodkin, Noam Camus Cc: linux-kernel, Vineet Gupta, Daniel Lezcano, Rob Herring, devicetree This allows us to introduce timers in DT in next commit Cc: Daniel Lezcano <daniel.lezcano@linaro.org> Cc: Rob Herring <robh@kernel.org> Cc: devicetree@vger.kernel.org Signed-off-by: Vineet Gupta <vgupta@synopsys.com> --- arch/arc/boot/dts/axc001.dtsi | 6 ++++++ arch/arc/boot/dts/axc003.dtsi | 6 ++++++ arch/arc/boot/dts/axc003_idu.dtsi | 6 ++++++ arch/arc/boot/dts/nsim_700.dts | 6 ++++++ arch/arc/boot/dts/nsim_hs.dts | 6 ++++++ arch/arc/boot/dts/nsim_hs_idu.dts | 6 ++++++ arch/arc/boot/dts/nsimosci.dts | 6 ++++++ arch/arc/boot/dts/nsimosci_hs.dts | 6 ++++++ arch/arc/boot/dts/nsimosci_hs_idu.dts | 6 ++++++ arch/arc/boot/dts/vdk_axc003.dtsi | 6 ++++++ arch/arc/boot/dts/vdk_axc003_idu.dtsi | 6 ++++++ 11 files changed, 66 insertions(+) diff --git a/arch/arc/boot/dts/axc001.dtsi b/arch/arc/boot/dts/axc001.dtsi index e7a83d19c5a3..40bcecfc3687 100644 --- a/arch/arc/boot/dts/axc001.dtsi +++ b/arch/arc/boot/dts/axc001.dtsi @@ -26,6 +26,12 @@ ranges = <0x00000000 0xf0000000 0x10000000>; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <750000000>; + }; + core_intc: arc700-intc@cpu { compatible = "snps,arc700-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/axc003.dtsi b/arch/arc/boot/dts/axc003.dtsi index b0e3ccdf8fc7..cabe0deeb2d8 100644 --- a/arch/arc/boot/dts/axc003.dtsi +++ b/arch/arc/boot/dts/axc003.dtsi @@ -25,6 +25,12 @@ ranges = <0x00000000 0xf0000000 0x10000000>; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <90000000>; + }; + core_intc: archs-intc@cpu { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/axc003_idu.dtsi b/arch/arc/boot/dts/axc003_idu.dtsi index f87ae409c8ed..8955881db794 100644 --- a/arch/arc/boot/dts/axc003_idu.dtsi +++ b/arch/arc/boot/dts/axc003_idu.dtsi @@ -25,6 +25,12 @@ ranges = <0x00000000 0xf0000000 0x10000000>; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <90000000>; + }; + core_intc: archs-intc@cpu { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/nsim_700.dts b/arch/arc/boot/dts/nsim_700.dts index 987921f711c1..5d5e373e0ebc 100644 --- a/arch/arc/boot/dts/nsim_700.dts +++ b/arch/arc/boot/dts/nsim_700.dts @@ -32,6 +32,12 @@ /* child and parent address space 1:1 mapped */ ranges; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <80000000>; + }; + core_intc: interrupt-controller { compatible = "snps,arc700-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/nsim_hs.dts b/arch/arc/boot/dts/nsim_hs.dts index bd46aec88c6a..cbd08fa38339 100644 --- a/arch/arc/boot/dts/nsim_hs.dts +++ b/arch/arc/boot/dts/nsim_hs.dts @@ -38,6 +38,12 @@ /* only perip space at end of low mem accessible */ ranges = <0x80000000 0x0 0x80000000 0x80000000>; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <80000000>; + }; + core_intc: core-interrupt-controller { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/nsim_hs_idu.dts b/arch/arc/boot/dts/nsim_hs_idu.dts index cc82781727a1..99eabe1a2bf6 100644 --- a/arch/arc/boot/dts/nsim_hs_idu.dts +++ b/arch/arc/boot/dts/nsim_hs_idu.dts @@ -29,6 +29,12 @@ /* child and parent address space 1:1 mapped */ ranges; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <80000000>; + }; + core_intc: core-interrupt-controller { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/nsimosci.dts b/arch/arc/boot/dts/nsimosci.dts index 1c169dc74ad1..bc3161ab8f82 100644 --- a/arch/arc/boot/dts/nsimosci.dts +++ b/arch/arc/boot/dts/nsimosci.dts @@ -35,6 +35,12 @@ /* child and parent address space 1:1 mapped */ ranges; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <20000000>; + }; + intc: interrupt-controller { compatible = "snps,arc700-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/nsimosci_hs.dts b/arch/arc/boot/dts/nsimosci_hs.dts index 9444956156d9..273dcce2cc66 100644 --- a/arch/arc/boot/dts/nsimosci_hs.dts +++ b/arch/arc/boot/dts/nsimosci_hs.dts @@ -35,6 +35,12 @@ /* child and parent address space 1:1 mapped */ ranges; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <20000000>; + }; + core_intc: core-interrupt-controller { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/nsimosci_hs_idu.dts b/arch/arc/boot/dts/nsimosci_hs_idu.dts index ff11388ee484..8fe60967a4c5 100644 --- a/arch/arc/boot/dts/nsimosci_hs_idu.dts +++ b/arch/arc/boot/dts/nsimosci_hs_idu.dts @@ -33,6 +33,12 @@ /* child and parent address space 1:1 mapped */ ranges; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <5000000>; + }; + core_intc: core-interrupt-controller { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/vdk_axc003.dtsi b/arch/arc/boot/dts/vdk_axc003.dtsi index 035759ee62a5..ad4ee43bd2ac 100644 --- a/arch/arc/boot/dts/vdk_axc003.dtsi +++ b/arch/arc/boot/dts/vdk_axc003.dtsi @@ -25,6 +25,12 @@ ranges = <0x00000000 0xf0000000 0x10000000>; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <50000000>; + }; + core_intc: archs-intc@cpu { compatible = "snps,archs-intc"; interrupt-controller; diff --git a/arch/arc/boot/dts/vdk_axc003_idu.dtsi b/arch/arc/boot/dts/vdk_axc003_idu.dtsi index 90e18f404889..a3cb6263c581 100644 --- a/arch/arc/boot/dts/vdk_axc003_idu.dtsi +++ b/arch/arc/boot/dts/vdk_axc003_idu.dtsi @@ -26,6 +26,12 @@ ranges = <0x00000000 0xf0000000 0x10000000>; + core_clk: core_clk { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <50000000>; + }; + core_intc: archs-intc@cpu { compatible = "snps,archs-intc"; interrupt-controller; -- 2.5.0 ^ permalink raw reply related [flat|nested] 13+ messages in thread
* [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] <1454410739-24444-1-git-send-email-vgupta@synopsys.com> 2016-02-02 10:58 ` [PATCH 1/9] ARC: [dts] Add clk feeding into timers to DTs Vineet Gupta @ 2016-02-02 10:58 ` Vineet Gupta [not found] ` <1454410739-24444-3-git-send-email-vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> 2016-02-02 13:15 ` Alexey Brodkin 1 sibling, 2 replies; 13+ messages in thread From: Vineet Gupta @ 2016-02-02 10:58 UTC (permalink / raw) To: linux-snps-arc, Alexey.Brodkin, Noam Camus Cc: linux-kernel, Vineet Gupta, Daniel Lezcano, Rob Herring, devicetree ARC Timers have historically been probed directly. As precursor to start probing Timers thru DT introduce these bindings Cc: Daniel Lezcano <daniel.lezcano@linaro.org> Cc: Rob Herring <robh@kernel.org> Cc: devicetree@vger.kernel.org Signed-off-by: Vineet Gupta <vgupta@synopsys.com> --- .../devicetree/bindings/timer/snps,arc-timer0.txt | 23 ++++++++++++++++++++++ .../devicetree/bindings/timer/snps,arc-timer1.txt | 17 ++++++++++++++++ .../devicetree/bindings/timer/snps,archs-gfrc.txt | 14 +++++++++++++ .../devicetree/bindings/timer/snps,archs-rtc.txt | 14 +++++++++++++ arch/arc/boot/dts/abilis_tb10x.dtsi | 12 +++++++++++ arch/arc/boot/dts/skeleton.dtsi | 12 +++++++++++ arch/arc/boot/dts/skeleton_hs.dtsi | 12 +++++++++++ arch/arc/boot/dts/skeleton_hs_idu.dtsi | 12 +++++++++++ 8 files changed, 116 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/snps,arc-timer0.txt create mode 100644 Documentation/devicetree/bindings/timer/snps,arc-timer1.txt create mode 100644 Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt create mode 100644 Documentation/devicetree/bindings/timer/snps,archs-rtc.txt diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt b/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt new file mode 100644 index 000000000000..ceb80c72a90b --- /dev/null +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt @@ -0,0 +1,23 @@ +Synopsys ARC Local Timer with Interrupt Capabilities +- Found on all ARC CPUs (ARC700/ARCHS) +- Mandatory clockevent provider + +Required properties: + +- compatible : should be "snps,arc-timer0" +- interrupts : single Interrupt going into parent intc + (16 for ARCHS cores, 3 for ARC700 cores) +- clocks : phandle to the source clock + +Optional properties: + +- interrupt-parent : phandle to parent intc + +Example: + + timer0: timer_clkevt { + compatible = "snps,arc-timer0"; + interrupts = <3>; + interrupt-parent = <&core_intc>; + clocks = <&timer0_clk>; + }; diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt new file mode 100644 index 000000000000..4886192ce2f2 --- /dev/null +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt @@ -0,0 +1,17 @@ +Synopsys ARC Free Running Local 32-bit Timer +- Found on all ARC CPUs (ARC700/ARCHS) +- Mandatory clocksource provider on ARC700 +- Optional clocksource provider on UP ARC HS CPUs + (and if better timer archs-rtc not available in SoC) + +Required properties: + +- compatible : should be "snps,arc-timer1" +- clocks : phandle to the source clock + +Example: + + timer1: timer_clksrc { + compatible = "snps,arc-timer1"; + clocks = <&timer0_clk>; + }; diff --git a/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt new file mode 100644 index 000000000000..cce60e16aa0d --- /dev/null +++ b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt @@ -0,0 +1,14 @@ +Synopsys ARC Free Running 64-bit Global Timer for ARC HS CPUs +- clocksourc provider for SMP SoC + +Required properties: + +- compatible : should be "snps,archs-gfrc" +- clocks : phandle to the source clock + +Example: + + timer1: timer_clksrc { + compatible = "snps,archs-gfrc"; + clocks = <&timer0_clk>; + }; diff --git a/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt new file mode 100644 index 000000000000..f3b49938812b --- /dev/null +++ b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt @@ -0,0 +1,14 @@ +Synopsys ARC Free Running 64-bit Local Timer for ARC HS CPUs +- clocksourc provider for UP SoC + +Required properties: + +- compatible : should be "snps,archs-rtc" +- clocks : phandle to the source clock + +Example: + + timer1: timer_clksrc { + compatible = "snps,arc-rtc"; + clocks = <&timer0_clk>; + }; diff --git a/arch/arc/boot/dts/abilis_tb10x.dtsi b/arch/arc/boot/dts/abilis_tb10x.dtsi index cfb5052239a1..f9f138efa92c 100644 --- a/arch/arc/boot/dts/abilis_tb10x.dtsi +++ b/arch/arc/boot/dts/abilis_tb10x.dtsi @@ -35,6 +35,18 @@ }; }; + timer0: timer_clkevt { + compatible = "snps,arc-timer0"; + interrupts = <3>; + interrupt-parent = <&intc>; + clocks = <&cpu_clk>; + }; + + timer1: timer_clksrc { + compatible = "snps,arc-timer1"; + clocks = <&cpu_clk>; + }; + soc100 { #address-cells = <1>; #size-cells = <1>; diff --git a/arch/arc/boot/dts/skeleton.dtsi b/arch/arc/boot/dts/skeleton.dtsi index 296d371a335c..bcb08b36210d 100644 --- a/arch/arc/boot/dts/skeleton.dtsi +++ b/arch/arc/boot/dts/skeleton.dtsi @@ -30,6 +30,18 @@ }; }; + timer0: timer_clkevt { + compatible = "snps,arc-timer0"; + interrupts = <3>; + interrupt-parent = <&core_intc>; + clocks = <&core_clk>; + }; + + timer1: timer_clksrc { + compatible = "snps,arc-timer1"; + clocks = <&core_clk>; + }; + memory { device_type = "memory"; reg = <0x80000000 0x10000000>; /* 256M */ diff --git a/arch/arc/boot/dts/skeleton_hs.dtsi b/arch/arc/boot/dts/skeleton_hs.dtsi index a53876669030..46c5b05aea90 100644 --- a/arch/arc/boot/dts/skeleton_hs.dtsi +++ b/arch/arc/boot/dts/skeleton_hs.dtsi @@ -25,6 +25,18 @@ }; }; + timer0: timer_clkevt { + compatible = "snps,arc-timer0"; + interrupts = <16>; + interrupt-parent = <&core_intc>; + clocks = <&core_clk>; + }; + + timer1: timer_clksrc { + compatible = "snps,arc-timer1"; + clocks = <&core_clk>; + }; + memory { device_type = "memory"; reg = <0x80000000 0x10000000>; /* 256M */ diff --git a/arch/arc/boot/dts/skeleton_hs_idu.dtsi b/arch/arc/boot/dts/skeleton_hs_idu.dtsi index 74898d017f7a..2a40bd9e2e2a 100644 --- a/arch/arc/boot/dts/skeleton_hs_idu.dtsi +++ b/arch/arc/boot/dts/skeleton_hs_idu.dtsi @@ -25,6 +25,18 @@ }; }; + timer0: timer_clkevt { + compatible = "snps,arc-timer0"; + interrupts = <16>; + interrupt-parent = <&core_intc>; + clocks = <&core_clk>; + }; + + timer1: timer_clksrc { + compatible = "snps,archs-timer-gfrc"; + clocks = <&core_clk>; + }; + memory { device_type = "memory"; reg = <0x80000000 0x10000000>; /* 256M */ -- 2.5.0 ^ permalink raw reply related [flat|nested] 13+ messages in thread
[parent not found: <1454410739-24444-3-git-send-email-vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>]
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <1454410739-24444-3-git-send-email-vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> @ 2016-02-02 12:48 ` Alexey Brodkin 2016-02-02 22:03 ` Rob Herring 1 sibling, 0 replies; 13+ messages in thread From: Alexey Brodkin @ 2016-02-02 12:48 UTC (permalink / raw) To: Vineet Gupta Cc: robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, noamc-d5a29ZRxExrQT0dZR+AlfA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1133 bytes --] Hi Vineet, On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: > ARC Timers have historically been probed directly. > As precursor to start probing Timers thru DT introduce these bindings > > Cc: Daniel Lezcano <daniel.lezcano@linaro.org> > Cc: Rob Herring <robh@kernel.org> > Cc: devicetree@vger.kernel.org > Signed-off-by: Vineet Gupta <vgupta@synopsys.com> > --- [snip] > +Required properties: > + > +- compatible : should be "snps,arc-timer0" > +- interrupts : single Interrupt going into parent intc > + (16 for ARCHS cores, 3 for ARC700 cores) > +- clocks : phandle to the source clock > + > +Optional properties: > + > +- interrupt-parent : phandle to parent intc > + > +Example: > + > + timer0: timer_clkevt { > + compatible = "snps,arc-timer0"; > + interrupts = <3>; > + interrupt-parent = <&core_intc>; > + clocks = <&timer0_clk>; Even though this is an example maybe we may use the same "core_clk" as in real .dts below? -AlexeyN‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·zøœzÚÞz)í…æèw*\x1fjg¬±¨\x1e¶‰šŽŠÝ¢j.ïÛ°\½½MŽúgjÌæa×\x02››–' ™©Þ¢¸\f¢·¦j:+v‰¨ŠwèjØm¶Ÿÿ¾\a«‘êçzZ+ƒùšŽŠÝ¢j"ú!¶i ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <1454410739-24444-3-git-send-email-vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> 2016-02-02 12:48 ` Alexey Brodkin @ 2016-02-02 22:03 ` Rob Herring 2016-02-03 8:04 ` Vineet Gupta 1 sibling, 1 reply; 13+ messages in thread From: Rob Herring @ 2016-02-02 22:03 UTC (permalink / raw) To: Vineet Gupta Cc: linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r, Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w, Noam Camus, linux-kernel-u79uwXL29TY76Z2rM5mHXA, Daniel Lezcano, devicetree-u79uwXL29TY76Z2rM5mHXA On Tue, Feb 02, 2016 at 04:28:52PM +0530, Vineet Gupta wrote: > ARC Timers have historically been probed directly. > As precursor to start probing Timers thru DT introduce these bindings > > Cc: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> > Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> > Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > Signed-off-by: Vineet Gupta <vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> > --- > .../devicetree/bindings/timer/snps,arc-timer0.txt | 23 ++++++++++++++++++++++ > .../devicetree/bindings/timer/snps,arc-timer1.txt | 17 ++++++++++++++++ > .../devicetree/bindings/timer/snps,archs-gfrc.txt | 14 +++++++++++++ > .../devicetree/bindings/timer/snps,archs-rtc.txt | 14 +++++++++++++ > arch/arc/boot/dts/abilis_tb10x.dtsi | 12 +++++++++++ > arch/arc/boot/dts/skeleton.dtsi | 12 +++++++++++ > arch/arc/boot/dts/skeleton_hs.dtsi | 12 +++++++++++ > arch/arc/boot/dts/skeleton_hs_idu.dtsi | 12 +++++++++++ > 8 files changed, 116 insertions(+) > create mode 100644 Documentation/devicetree/bindings/timer/snps,arc-timer0.txt > create mode 100644 Documentation/devicetree/bindings/timer/snps,arc-timer1.txt > create mode 100644 Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt > create mode 100644 Documentation/devicetree/bindings/timer/snps,archs-rtc.txt > > diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt b/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt > new file mode 100644 > index 000000000000..ceb80c72a90b > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt > @@ -0,0 +1,23 @@ > +Synopsys ARC Local Timer with Interrupt Capabilities > +- Found on all ARC CPUs (ARC700/ARCHS) > +- Mandatory clockevent provider > + > +Required properties: > + > +- compatible : should be "snps,arc-timer0" timer0 and timer1 are different h/w blocks, not just different instances? > +- interrupts : single Interrupt going into parent intc > + (16 for ARCHS cores, 3 for ARC700 cores) > +- clocks : phandle to the source clock > + > +Optional properties: > + > +- interrupt-parent : phandle to parent intc > + > +Example: > + > + timer0: timer_clkevt { just "timer" for node name. clkevt is a Linuxism. > + compatible = "snps,arc-timer0"; > + interrupts = <3>; > + interrupt-parent = <&core_intc>; > + clocks = <&timer0_clk>; > + }; > diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt > new file mode 100644 > index 000000000000..4886192ce2f2 > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt > @@ -0,0 +1,17 @@ > +Synopsys ARC Free Running Local 32-bit Timer > +- Found on all ARC CPUs (ARC700/ARCHS) > +- Mandatory clocksource provider on ARC700 > +- Optional clocksource provider on UP ARC HS CPUs > + (and if better timer archs-rtc not available in SoC) > + > +Required properties: > + > +- compatible : should be "snps,arc-timer1" > +- clocks : phandle to the source clock No interrupt because it doesn't have one or you use this as a clocksource and don't need it? > + > +Example: > + > + timer1: timer_clksrc { > + compatible = "snps,arc-timer1"; > + clocks = <&timer0_clk>; > + }; > diff --git a/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt > new file mode 100644 > index 000000000000..cce60e16aa0d > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt > @@ -0,0 +1,14 @@ > +Synopsys ARC Free Running 64-bit Global Timer for ARC HS CPUs > +- clocksourc provider for SMP SoC > + > +Required properties: > + > +- compatible : should be "snps,archs-gfrc" > +- clocks : phandle to the source clock > + > +Example: > + > + timer1: timer_clksrc { > + compatible = "snps,archs-gfrc"; > + clocks = <&timer0_clk>; > + }; > diff --git a/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt > new file mode 100644 > index 000000000000..f3b49938812b > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt > @@ -0,0 +1,14 @@ > +Synopsys ARC Free Running 64-bit Local Timer for ARC HS CPUs > +- clocksourc provider for UP SoC local timer on a UP processor? > + > +Required properties: > + > +- compatible : should be "snps,archs-rtc" > +- clocks : phandle to the source clock > + > +Example: > + > + timer1: timer_clksrc { > + compatible = "snps,arc-rtc"; > + clocks = <&timer0_clk>; > + }; -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings 2016-02-02 22:03 ` Rob Herring @ 2016-02-03 8:04 ` Vineet Gupta [not found] ` <C2D7FE5348E1B147BCA15975FBA23075F4E87B33-cALIpNOex2c3t6iM5Z/N3fufCSb+aD3WLzEdoUbNIic@public.gmane.org> 0 siblings, 1 reply; 13+ messages in thread From: Vineet Gupta @ 2016-02-03 8:04 UTC (permalink / raw) To: Rob Herring Cc: arcml, Alexey Brodkin, Noam Camus, lkml, Daniel Lezcano, devicetree@vger.kernel.org Hi Rob, On Wednesday 03 February 2016 03:33 AM, Rob Herring wrote: > On Tue, Feb 02, 2016 at 04:28:52PM +0530, Vineet Gupta wrote: >> +Required properties: >> + >> +- compatible : should be "snps,arc-timer0" > > timer0 and timer1 are different h/w blocks, not just different > instances? Functionality wise they are identical (only the address of aux regs used to program them are different). Either can be configured to interrupt-on-limit or free-run-and-wrap-around. So we can indeed consider them 2 instances. ARC Linux uses timer0 for tick handling, timer1 for gtod. Do you prefer they not be differentiated as timer0 and timer1 ? So we have CLOCKSOURCE_OF_DECLARE(arc_clkevt, "snps,arc-timer0", arc_clockevent_setup); CLOCKSOURCE_OF_DECLARE(arc_timer1, "snps,arc-timer1", arc_cs_setup_timer1); I don't know how to achieve above, by keeping the DT names the same. > >> +- interrupts : single Interrupt going into parent intc >> + (16 for ARCHS cores, 3 for ARC700 cores) >> +- clocks : phandle to the source clock >> + >> +Optional properties: >> + >> +- interrupt-parent : phandle to parent intc >> + >> +Example: >> + >> + timer0: timer_clkevt { > > just "timer" for node name. clkevt is a Linuxism. OK. So to document that this is for clockevent, change the label ? timer_clkevent: timer { > >> + compatible = "snps,arc-timer0"; >> + interrupts = <3>; >> + interrupt-parent = <&core_intc>; >> + clocks = <&timer0_clk>; >> + }; >> diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt >> new file mode 100644 >> index 000000000000..4886192ce2f2 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt >> @@ -0,0 +1,17 @@ >> +Synopsys ARC Free Running Local 32-bit Timer >> +- Found on all ARC CPUs (ARC700/ARCHS) >> +- Mandatory clocksource provider on ARC700 >> +- Optional clocksource provider on UP ARC HS CPUs >> + (and if better timer archs-rtc not available in SoC) >> + >> +Required properties: >> + >> +- compatible : should be "snps,arc-timer1" >> +- clocks : phandle to the source clock > > No interrupt because it doesn't have one or you use this as a > clocksource and don't need it? Latter ! >> + >> +Example: >> + >> + timer1: timer_clksrc { >> + compatible = "snps,arc-timer1"; >> + clocks = <&timer0_clk>; >> + }; >> diff --git a/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt >> new file mode 100644 >> index 000000000000..cce60e16aa0d >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt >> @@ -0,0 +1,14 @@ >> +Synopsys ARC Free Running 64-bit Global Timer for ARC HS CPUs >> +- clocksourc provider for SMP SoC >> + >> +Required properties: >> + >> +- compatible : should be "snps,archs-gfrc" >> +- clocks : phandle to the source clock >> + >> +Example: >> + >> + timer1: timer_clksrc { >> + compatible = "snps,archs-gfrc"; >> + clocks = <&timer0_clk>; >> + }; >> diff --git a/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt >> new file mode 100644 >> index 000000000000..f3b49938812b >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt >> @@ -0,0 +1,14 @@ >> +Synopsys ARC Free Running 64-bit Local Timer for ARC HS CPUs >> +- clocksourc provider for UP SoC > > local timer on a UP processor? Not sure what you mean to change. This timer could be present in UP or SMP hardware configs but only usable as clocksource for UP since it is local and we don't do tick broadcast etc for SMP. To me clocksource is one level higher in level of abstraction than processor and thus applies to overall system / SoC than the processor. Thx, -Vineet >> +Required properties: >> + >> +- compatible : should be "snps,archs-rtc" >> +- clocks : phandle to the source clock >> + >> +Example: >> + >> + timer1: timer_clksrc { >> + compatible = "snps,arc-rtc"; >> + clocks = <&timer0_clk>; >> + }; > -- ^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <C2D7FE5348E1B147BCA15975FBA23075F4E87B33-cALIpNOex2c3t6iM5Z/N3fufCSb+aD3WLzEdoUbNIic@public.gmane.org>]
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <C2D7FE5348E1B147BCA15975FBA23075F4E87B33-cALIpNOex2c3t6iM5Z/N3fufCSb+aD3WLzEdoUbNIic@public.gmane.org> @ 2016-02-03 15:39 ` Rob Herring [not found] ` <CAL_Jsq+15SERAN8B5vcKVG=O8=pLLw5_0-p2STHjyGUu7mx-7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 13+ messages in thread From: Rob Herring @ 2016-02-03 15:39 UTC (permalink / raw) To: Vineet Gupta Cc: arcml, Alexey Brodkin, Noam Camus, lkml, Daniel Lezcano, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Wed, Feb 3, 2016 at 2:04 AM, Vineet Gupta <Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> wrote: > Hi Rob, > > On Wednesday 03 February 2016 03:33 AM, Rob Herring wrote: >> On Tue, Feb 02, 2016 at 04:28:52PM +0530, Vineet Gupta wrote: >>> +Required properties: >>> + >>> +- compatible : should be "snps,arc-timer0" >> >> timer0 and timer1 are different h/w blocks, not just different >> instances? > > Functionality wise they are identical (only the address of aux regs used to > program them are different). Either can be configured to interrupt-on-limit or > free-run-and-wrap-around. So we can indeed consider them 2 instances. ARC Linux > uses timer0 for tick handling, timer1 for gtod. > > Do you prefer they not be differentiated as timer0 and timer1 ? > > So we have > > CLOCKSOURCE_OF_DECLARE(arc_clkevt, "snps,arc-timer0", arc_clockevent_setup); > CLOCKSOURCE_OF_DECLARE(arc_timer1, "snps,arc-timer1", arc_cs_setup_timer1); > > I don't know how to achieve above, by keeping the DT names the same. You just need a single CLOCKSOURCE_OF_DECLARE which will be called twice. On the first call, setup one timer and on the 2nd call setup the other one. IIRC the sp804 timer has something similar. You'll need a unit address in the node name to distinguish them. > >> >>> +- interrupts : single Interrupt going into parent intc >>> + (16 for ARCHS cores, 3 for ARC700 cores) >>> +- clocks : phandle to the source clock >>> + >>> +Optional properties: >>> + >>> +- interrupt-parent : phandle to parent intc >>> + >>> +Example: >>> + >>> + timer0: timer_clkevt { >> >> just "timer" for node name. clkevt is a Linuxism. > > OK. So to document that this is for clockevent, change the label ? That shouldn't be documented in the DT at all. > > timer_clkevent: timer { > >> >>> + compatible = "snps,arc-timer0"; >>> + interrupts = <3>; >>> + interrupt-parent = <&core_intc>; >>> + clocks = <&timer0_clk>; >>> + }; >>> diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt >>> new file mode 100644 >>> index 000000000000..4886192ce2f2 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt >>> @@ -0,0 +1,17 @@ >>> +Synopsys ARC Free Running Local 32-bit Timer >>> +- Found on all ARC CPUs (ARC700/ARCHS) >>> +- Mandatory clocksource provider on ARC700 >>> +- Optional clocksource provider on UP ARC HS CPUs >>> + (and if better timer archs-rtc not available in SoC) >>> + >>> +Required properties: >>> + >>> +- compatible : should be "snps,arc-timer1" >>> +- clocks : phandle to the source clock >> >> No interrupt because it doesn't have one or you use this as a >> clocksource and don't need it? > > Latter ! Then you should have the interrupt in the DT anyway. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <CAL_Jsq+15SERAN8B5vcKVG=O8=pLLw5_0-p2STHjyGUu7mx-7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <CAL_Jsq+15SERAN8B5vcKVG=O8=pLLw5_0-p2STHjyGUu7mx-7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2016-02-16 8:44 ` Vineet Gupta 0 siblings, 0 replies; 13+ messages in thread From: Vineet Gupta @ 2016-02-16 8:44 UTC (permalink / raw) To: Rob Herring Cc: arcml, Alexey Brodkin, Noam Camus, lkml, Daniel Lezcano, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Wednesday 03 February 2016 09:09 PM, Rob Herring wrote: > On Wed, Feb 3, 2016 at 2:04 AM, Vineet Gupta <Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> wrote: >> Hi Rob, >> >> On Wednesday 03 February 2016 03:33 AM, Rob Herring wrote: >>> On Tue, Feb 02, 2016 at 04:28:52PM +0530, Vineet Gupta wrote: >>>> +Required properties: >>>> + >>>> +- compatible : should be "snps,arc-timer0" >>> >>> timer0 and timer1 are different h/w blocks, not just different >>> instances? >> >> Functionality wise they are identical (only the address of aux regs used to >> program them are different). Either can be configured to interrupt-on-limit or >> free-run-and-wrap-around. So we can indeed consider them 2 instances. ARC Linux >> uses timer0 for tick handling, timer1 for gtod. >> >> Do you prefer they not be differentiated as timer0 and timer1 ? >> >> So we have >> >> CLOCKSOURCE_OF_DECLARE(arc_clkevt, "snps,arc-timer0", arc_clockevent_setup); >> CLOCKSOURCE_OF_DECLARE(arc_timer1, "snps,arc-timer1", arc_cs_setup_timer1); >> >> I don't know how to achieve above, by keeping the DT names the same. > > You just need a single CLOCKSOURCE_OF_DECLARE which will be called > twice. On the first call, setup one timer and on the 2nd call setup > the other one. IIRC the sp804 timer has something similar. > > You'll need a unit address in the node name to distinguish them. So this is just to distinguish them in DT, but the callback uses a static counter to do 1st vs. 2nd (and this unit address is not really exposed to code) - correct ? -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings 2016-02-02 10:58 ` [PATCH 2/9] ARC: [dts] Introduce Timer bindings Vineet Gupta [not found] ` <1454410739-24444-3-git-send-email-vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> @ 2016-02-02 13:15 ` Alexey Brodkin 2016-02-02 14:29 ` Vineet Gupta 1 sibling, 1 reply; 13+ messages in thread From: Alexey Brodkin @ 2016-02-02 13:15 UTC (permalink / raw) To: Vineet Gupta Cc: robh@kernel.org, linux-kernel@vger.kernel.org, daniel.lezcano@linaro.org, noamc@ezchip.com, devicetree@vger.kernel.org, linux-snps-arc@lists.infradead.org Hi Vineet, On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: > ARC Timers have historically been probed directly. > As precursor to start probing Timers thru DT introduce these bindings > > Cc: Daniel Lezcano <daniel.lezcano@linaro.org> > Cc: Rob Herring <robh@kernel.org> > Cc: devicetree@vger.kernel.org > Signed-off-by: Vineet Gupta <vgupta@synopsys.com> > --- [snip] > diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt > b/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt > new file mode 100644 > index 000000000000..ceb80c72a90b > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer0.txt > @@ -0,0 +1,23 @@ > +Synopsys ARC Local Timer with Interrupt Capabilities > +- Found on all ARC CPUs (ARC700/ARCHS) > +- Mandatory clockevent provider > + > +Required properties: > + > +- compatible : should be "snps,arc-timer0" > +- interrupts : single Interrupt going into parent intc > + (16 for ARCHS cores, 3 for ARC700 cores) > +- clocks : phandle to the source clock Actually we're not flexible here. See we have hard-coded "core_clk" in [PATCH 8/9]. We use it directly in show_cpuinfo() for reading clock speed as well as in axs103_early_init(). So "source clock" here MUST be "core_clk", otherwise /proc/cpuinfo will report junk instead of meaningful data at least. > + > +Optional properties: > + > +- interrupt-parent : phandle to parent intc > + > +Example: > + > + timer0: timer_clkevt { > + compatible = "snps,arc-timer0"; > + interrupts = <3>; > + interrupt-parent = <&core_intc>; > + clocks = <&timer0_clk>; > + }; > diff --git a/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt > b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt > new file mode 100644 > index 000000000000..4886192ce2f2 > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,arc-timer1.txt > @@ -0,0 +1,17 @@ > +Synopsys ARC Free Running Local 32-bit Timer > +- Found on all ARC CPUs (ARC700/ARCHS) > +- Mandatory clocksource provider on ARC700 > +- Optional clocksource provider on UP ARC HS CPUs > + (and if better timer archs-rtc not available in SoC) > + > +Required properties: > + > +- compatible : should be "snps,arc-timer1" > +- clocks : phandle to the source clock > + > +Example: > + > + timer1: timer_clksrc { > + compatible = "snps,arc-timer1"; > + clocks = <&timer0_clk>; Ditto, "clocks = <&core_clk>". > + }; > diff --git a/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt > b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt > new file mode 100644 > index 000000000000..cce60e16aa0d > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt > @@ -0,0 +1,14 @@ > +Synopsys ARC Free Running 64-bit Global Timer for ARC HS CPUs > +- clocksourc provider for SMP SoC > + > +Required properties: > + > +- compatible : should be "snps,archs-gfrc" > +- clocks : phandle to the source clock > + > +Example: > + > + timer1: timer_clksrc { > + compatible = "snps,archs-gfrc"; > + clocks = <&timer0_clk>; Ditto, "clocks = <&core_clk>". > + }; > diff --git a/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt > b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt > new file mode 100644 > index 000000000000..f3b49938812b > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/snps,archs-rtc.txt > @@ -0,0 +1,14 @@ > +Synopsys ARC Free Running 64-bit Local Timer for ARC HS CPUs > +- clocksourc provider for UP SoC > + > +Required properties: > + > +- compatible : should be "snps,archs-rtc" > +- clocks : phandle to the source clock > + > +Example: > + > + timer1: timer_clksrc { > + compatible = "snps,arc-rtc"; > + clocks = <&timer0_clk>; > + }; > diff --git a/arch/arc/boot/dts/abilis_tb10x.dtsi b/arch/arc/boot/dts/abilis_tb10x.dtsi > index cfb5052239a1..f9f138efa92c 100644 > --- a/arch/arc/boot/dts/abilis_tb10x.dtsi > +++ b/arch/arc/boot/dts/abilis_tb10x.dtsi > @@ -35,6 +35,18 @@ > }; > }; > > + timer0: timer_clkevt { > + compatible = "snps,arc-timer0"; > + interrupts = <3>; > + interrupt-parent = <&intc>; > + clocks = <&cpu_clk>; > > + }; > + > + timer1: timer_clksrc { > + compatible = "snps,arc-timer1"; > + clocks = <&cpu_clk>; > + }; > + Hm now that's a question how to fix /proc/cpuinfo output for Abilis? There's no "core_clk" DTS node for Abilis and so show_cpuinfo() won't get proper clock value. Probably we may fix it with modification of their "pll" node from ------------------------>8---------------------- pll0: oscillator { clock-frequency = <1000000000>; }; ------------------------>8---------------------- to ------------------------>8---------------------- core_clk: oscillator { clock -frequency = <1000000000>; }; ------------------------>8---------------------- -Alexey ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings 2016-02-02 13:15 ` Alexey Brodkin @ 2016-02-02 14:29 ` Vineet Gupta [not found] ` <56B0BD2F.5080409-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> 0 siblings, 1 reply; 13+ messages in thread From: Vineet Gupta @ 2016-02-02 14:29 UTC (permalink / raw) To: Alexey Brodkin, Vineet Gupta Cc: robh@kernel.org, linux-kernel@vger.kernel.org, daniel.lezcano@linaro.org, noamc@ezchip.com, devicetree@vger.kernel.org, linux-snps-arc@lists.infradead.org Hi Alexey, On Tuesday 02 February 2016 06:45 PM, Alexey Brodkin wrote: > Hi Vineet, > > On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: >> + >> +Required properties: >> + >> +- compatible : should be "snps,arc-timer0" >> +- interrupts : single Interrupt going into parent intc >> + (16 for ARCHS cores, 3 for ARC700 cores) >> +- clocks : phandle to the source clock > > Actually we're not flexible here. > See we have hard-coded "core_clk" in [PATCH 8/9]. > We use it directly in show_cpuinfo() for reading clock speed > as well as in axs103_early_init(). > > So "source clock" here MUST be "core_clk", otherwise > /proc/cpuinfo will report junk instead of meaningful data at least. Using hardcoded DT names in generic code is total BS and I slap myself for missing that in reviewing 8/9. Please fix it ! FWIW, it is OK to have such hardcoding in say AXS103 DTS and AXS103 platform code but it is not the way to go in setup.c >> +Required properties: >> + >> +- compatible : should be "snps,arc-timer1" >> +- clocks : phandle to the source clock >> + >> +Example: >> + >> + timer1: timer_clksrc { >> + compatible = "snps,arc-timer1"; >> + clocks = <&timer0_clk>; > > Ditto, "clocks = <&core_clk>". Yeah I fixed all those ! >> diff --git a/arch/arc/boot/dts/abilis_tb10x.dtsi b/arch/arc/boot/dts/abilis_tb10x.dtsi >> index cfb5052239a1..f9f138efa92c 100644 >> --- a/arch/arc/boot/dts/abilis_tb10x.dtsi >> +++ b/arch/arc/boot/dts/abilis_tb10x.dtsi >> @@ -35,6 +35,18 @@ >> }; >> }; >> >> + timer0: timer_clkevt { >> + compatible = "snps,arc-timer0"; >> + interrupts = <3>; >> + interrupt-parent = <&intc>; >> + clocks = <&cpu_clk>; >> >> + }; >> + >> + timer1: timer_clksrc { >> + compatible = "snps,arc-timer1"; >> + clocks = <&cpu_clk>; >> + }; >> + > > Hm now that's a question how to fix /proc/cpuinfo output > for Abilis? There's no "core_clk" DTS node for Abilis and so > show_cpuinfo() won't get proper clock value. > > Probably we may fix it with modification of their "pll" node > from > ------------------------>8---------------------- > pll0: oscillator { > clock-frequency = <1000000000>; > }; > ------------------------>8---------------------- > > to > ------------------------>8---------------------- > core_clk: oscillator { > clock > -frequency = <1000000000>; > }; > ------------------------>8---------------------- This is all moot once we fix the orig problem. ^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <56B0BD2F.5080409-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>]
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <56B0BD2F.5080409-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> @ 2016-02-02 15:36 ` Alexey Brodkin [not found] ` <1454427373.25997.24.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> 0 siblings, 1 reply; 13+ messages in thread From: Alexey Brodkin @ 2016-02-02 15:36 UTC (permalink / raw) To: Vineet Gupta Cc: robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, noamc-d5a29ZRxExrQT0dZR+AlfA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1337 bytes --] Hi Vineet, On Tue, 2016-02-02 at 19:59 +0530, Vineet Gupta wrote: > Hi Alexey, > > On Tuesday 02 February 2016 06:45 PM, Alexey Brodkin wrote: > > Hi Vineet, > > > > On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: > > > + > > > +Required properties: > > > + > > > +- compatible : should be "snps,arc-timer0" > > > +- interrupts : single Interrupt going into parent intc > > > + (16 for ARCHS cores, 3 for ARC700 cores) > > > +- clocks : phandle to the source clock > > > > Actually we're not flexible here. > > See we have hard-coded "core_clk" in [PATCH 8/9]. > > We use it directly in show_cpuinfo() for reading clock speed > > as well as in axs103_early_init(). > > > > So "source clock" here MUST be "core_clk", otherwise > > /proc/cpuinfo will report junk instead of meaningful data at least. > > Using hardcoded DT names in generic code is total BS and I slap myself for missing > that in reviewing 8/9. Please fix it ! But the only other alternative to hard-coded name is use of some internal variable like "arc_timer_freq". I.e. we make "arc_timer_freq" global and use it for displaying core frequency. Are you OK with that? -AlexeyN‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·zøœzÚÞz)í…æèw*\x1fjg¬±¨\x1e¶‰šŽŠÝ¢j.ïÛ°\½½MŽúgjÌæa×\x02››–' ™©Þ¢¸\f¢·¦j:+v‰¨ŠwèjØm¶Ÿÿ¾\a«‘êçzZ+ƒùšŽŠÝ¢j"ú!¶i ^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <1454427373.25997.24.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>]
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <1454427373.25997.24.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> @ 2016-02-02 22:57 ` Alexey Brodkin 2016-02-03 13:44 ` Alexey Brodkin 0 siblings, 1 reply; 13+ messages in thread From: Alexey Brodkin @ 2016-02-02 22:57 UTC (permalink / raw) To: Vineet Gupta Cc: robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, noamc-d5a29ZRxExrQT0dZR+AlfA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1643 bytes --] Hi Vineet, On Tue, 2016-02-02 at 18:36 +0300, Alexey Brodkin wrote: > Hi Vineet, > > On Tue, 2016-02-02 at 19:59 +0530, Vineet Gupta wrote: > > Hi Alexey, > > > > On Tuesday 02 February 2016 06:45 PM, Alexey Brodkin wrote: > > > Hi Vineet, > > > > > > On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: > > > > + > > > > +Required properties: > > > > + > > > > +- compatible : should be "snps,arc-timer0" > > > > +- interrupts : single Interrupt going into parent intc > > > > + (16 for ARCHS cores, 3 for ARC700 cores) > > > > +- clocks : phandle to the source clock > > > > > > Actually we're not flexible here. > > > See we have hard-coded "core_clk" in [PATCH 8/9]. > > > We use it directly in show_cpuinfo() for reading clock speed > > > as well as in axs103_early_init(). > > > > > > So "source clock" here MUST be "core_clk", otherwise > > > /proc/cpuinfo will report junk instead of meaningful data at least. > > > > Using hardcoded DT names in generic code is total BS and I slap myself for missing > > that in reviewing 8/9. Please fix it ! > > But the only other alternative to hard-coded name is use of some internal variable > like "arc_timer_freq". > > I.e. we make "arc_timer_freq" global and use it for displaying core frequency. Well actually there's another possibility that is used on many other platforms (ARM both 32 and 64-bit flavors is a good example) - just print bogomips instead of additional core frequency. -AlexeyN‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·zøœzÚÞz)í…æèw*\x1fjg¬±¨\x1e¶‰šŽŠÝ¢j.ïÛ°\½½MŽúgjÌæa×\x02››–' ™©Þ¢¸\f¢·¦j:+v‰¨ŠwèjØm¶Ÿÿ¾\a«‘êçzZ+ƒùšŽŠÝ¢j"ú!¶i ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings 2016-02-02 22:57 ` Alexey Brodkin @ 2016-02-03 13:44 ` Alexey Brodkin [not found] ` <1454507041.3375.39.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> 0 siblings, 1 reply; 13+ messages in thread From: Alexey Brodkin @ 2016-02-03 13:44 UTC (permalink / raw) To: mturquette@ti.com Cc: robh@kernel.org, linux-kernel@vger.kernel.org, daniel.lezcano@linaro.org, noamc@ezchip.com, Vineet Gupta, devicetree@vger.kernel.org, linux-snps-arc@lists.infradead.org Hi Mike, On Wed, 2016-02-03 at 01:57 +0300, Alexey Brodkin wrote: > Hi Vineet, > > On Tue, 2016-02-02 at 18:36 +0300, Alexey Brodkin wrote: > > Hi Vineet, > > > > On Tue, 2016-02-02 at 19:59 +0530, Vineet Gupta wrote: > > > Hi Alexey, > > > > > > On Tuesday 02 February 2016 06:45 PM, Alexey Brodkin wrote: > > > > Hi Vineet, > > > > > > > > On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: > > > > > + > > > > > +Required properties: > > > > > + > > > > > +- compatible : should be "snps,arc-timer0" > > > > > +- interrupts : single Interrupt going into parent intc > > > > > + (16 for ARCHS cores, 3 for ARC700 cores) > > > > > +- clocks : phandle to the source clock > > > > > > > > Actually we're not flexible here. > > > > See we have hard-coded "core_clk" in [PATCH 8/9]. > > > > We use it directly in show_cpuinfo() for reading clock speed > > > > as well as in axs103_early_init(). > > > > > > > > So "source clock" here MUST be "core_clk", otherwise > > > > /proc/cpuinfo will report junk instead of meaningful data at least. > > > > > > Using hardcoded DT names in generic code is total BS and I slap myself for missing > > > that in reviewing 8/9. Please fix it ! > > > > But the only other alternative to hard-coded name is use of some internal variable > > like "arc_timer_freq". > > > > I.e. we make "arc_timer_freq" global and use it for displaying core frequency. > > Well actually there's another possibility that is used on many other platforms > (ARM both 32 and 64-bit flavors is a good example) - just print bogomips instead > of additional core frequency. We're in the process of switching ARC to generic clk framework. One of the problems we're trying to solve now is how to obtain precise CPU frequency value for outputting it for example by /proc/cpuinfo. This precise (in terms of what value was set via Device Tree or extracted and decoded from CPU configuration registers) CPU frequency is very useful for example for benchmarking. In comparison bogomips might be misleading at times. Before moving to clk framework we used to have 2 ARC-specific calls arc_get_core_freq() and arc_set_core_freq() which were basically wrappers for one variable where we stored CPU frequency. I took a look at what other architectures do and so far saw these options: [1] Just print bogomips (ARM both 32- and 64-bit, m64k, Microblaze, Mips, mn10300, openrisc, s390, sh, um, unicore32, ) [2] Get frequency from some kind of architecture-specific structure or variable (Alpha, AVR32, c6x, nios2, powerpc, sparc, tile, xtensa) [3] Get frequency from cpufreq framework (ia64, x86) [4] Decode frequency from hardware registers (Blackfin) Any thoughts on what's the best way to get CPU frequency in run-time (preferably with use of clk framework so we'll need no arch-specific variables)? Regards, Alexey ^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <1454507041.3375.39.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>]
* Re: [PATCH 2/9] ARC: [dts] Introduce Timer bindings [not found] ` <1454507041.3375.39.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> @ 2016-02-03 13:50 ` Alexey Brodkin 0 siblings, 0 replies; 13+ messages in thread From: Alexey Brodkin @ 2016-02-03 13:50 UTC (permalink / raw) To: mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org Cc: robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, noamc-d5a29ZRxExrQT0dZR+AlfA@public.gmane.org, Vineet Gupta, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org (re-sending because Mike's email @ti is no longer valid) Hi Mike, On Wed, 2016-02-03 at 01:57 +0300, Alexey Brodkin wrote: > Hi Vineet, > > On Tue, 2016-02-02 at 18:36 +0300, Alexey Brodkin wrote: > > Hi Vineet, > > > > On Tue, 2016-02-02 at 19:59 +0530, Vineet Gupta wrote: > > > Hi Alexey, > > > > > > On Tuesday 02 February 2016 06:45 PM, Alexey Brodkin wrote: > > > > Hi Vineet, > > > > > > > > On Tue, 2016-02-02 at 16:28 +0530, Vineet Gupta wrote: > > > > > + > > > > > +Required properties: > > > > > + > > > > > +- compatible : should be "snps,arc-timer0" > > > > > +- interrupts : single Interrupt going into parent intc > > > > > + (16 for ARCHS cores, 3 for ARC700 cores) > > > > > +- clocks : phandle to the source clock > > > > > > > > Actually we're not flexible here. > > > > See we have hard-coded "core_clk" in [PATCH 8/9]. > > > > We use it directly in show_cpuinfo() for reading clock speed > > > > as well as in axs103_early_init(). > > > > > > > > So "source clock" here MUST be "core_clk", otherwise > > > > /proc/cpuinfo will report junk instead of meaningful data at least. > > > > > > Using hardcoded DT names in generic code is total BS and I slap myself for missing > > > that in reviewing 8/9. Please fix it ! > > > > But the only other alternative to hard-coded name is use of some internal variable > > like "arc_timer_freq". > > > > I.e. we make "arc_timer_freq" global and use it for displaying core frequency. > > Well actually there's another possibility that is used on many other platforms > (ARM both 32 and 64-bit flavors is a good example) - just print bogomips instead > of additional core frequency. We're in the process of switching ARC to generic clk framework. One of the problems we're trying to solve now is how to obtain precise CPU frequency value for outputting it for example by /proc/cpuinfo. This precise (in terms of what value was set via Device Tree or extracted and decoded from CPU configuration registers) CPU frequency is very useful for example for benchmarking. In comparison bogomips might be misleading at times. Before moving to clk framework we used to have 2 ARC-specific calls arc_get_core_freq() and arc_set_core_freq() which were basically wrappers for one variable where we stored CPU frequency. I took a look at what other architectures do and so far saw these options: [1] Just print bogomips (ARM both 32- and 64-bit, m64k, Microblaze, Mips, mn10300, openrisc, s390, sh, um, unicore32, ) [2] Get frequency from some kind of architecture-specific structure or variable (Alpha, AVR32, c6x, nios2, powerpc, sparc, tile, xtensa) [3] Get frequency from cpufreq framework (ia64, x86) [4] Decode frequency from hardware registers (Blackfin) Any thoughts on what's the best way to get CPU frequency in run-time (preferably with use of clk framework so we'll need no arch-specific variables)? Regards, Alexey ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2016-02-16 8:44 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1454410739-24444-1-git-send-email-vgupta@synopsys.com>
2016-02-02 10:58 ` [PATCH 1/9] ARC: [dts] Add clk feeding into timers to DTs Vineet Gupta
2016-02-02 10:58 ` [PATCH 2/9] ARC: [dts] Introduce Timer bindings Vineet Gupta
[not found] ` <1454410739-24444-3-git-send-email-vgupta-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-02-02 12:48 ` Alexey Brodkin
2016-02-02 22:03 ` Rob Herring
2016-02-03 8:04 ` Vineet Gupta
[not found] ` <C2D7FE5348E1B147BCA15975FBA23075F4E87B33-cALIpNOex2c3t6iM5Z/N3fufCSb+aD3WLzEdoUbNIic@public.gmane.org>
2016-02-03 15:39 ` Rob Herring
[not found] ` <CAL_Jsq+15SERAN8B5vcKVG=O8=pLLw5_0-p2STHjyGUu7mx-7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-16 8:44 ` Vineet Gupta
2016-02-02 13:15 ` Alexey Brodkin
2016-02-02 14:29 ` Vineet Gupta
[not found] ` <56B0BD2F.5080409-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-02-02 15:36 ` Alexey Brodkin
[not found] ` <1454427373.25997.24.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-02-02 22:57 ` Alexey Brodkin
2016-02-03 13:44 ` Alexey Brodkin
[not found] ` <1454507041.3375.39.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-02-03 13:50 ` Alexey Brodkin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).