Hi Chris,
On Thu, Mar 16, 2017 at 6:51 PM, Chris Brandt <[email protected]> wrote:
> rtc-sh is a RTC for SuperH and RZ/A SoCs.
an RTC?
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/rtc-sh.txt
> @@ -0,0 +1,19 @@
> +* Real Time Clock for Renesas SH and ARM SoCs
> +
> +Required properties:
> +- compatible: Should be "renesas,r7s72100-rtc" or "renesas,sh-rtc" as a
s/or/and/
> + fallback.
> +- reg: physical base address and length of memory mapped region.
> +- interrupts: 3 interrupts for alarm, period, and carry.
If there's a need for multiple interrupts, it's always a good idea to use
interrupt-names. The datasheet calls them "arm", "prd", and "cup", but
I wouldn't object against "alarm", "period", and "carry" ;-)
> +- clocks: the clock source for the RTC controller.
The datasheet mentions 3 possible clock sources?
> +Example:
> +rtc: rtc@fcff1000 {
> + compatible = "renesas,r7s72100-rtc", "renesas,sh-rtc";
> + reg = <0xfcff1000 0x2e>;
> + interrupts = <GIC_SPI 276 IRQ_TYPE_EDGE_RISING
> + GIC_SPI 277 IRQ_TYPE_EDGE_RISING
> + GIC_SPI 278 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&mstp6_clks R7S72100_CLK_RTC>;
> + power-domains = <&cpg_clocks>;
> +};
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
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
