Searched hist:04421420 (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/arc/configs/ |
| H A D | vdk_hs38_smp_defconfig | 04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
|
| H A D | nsimosci_hs_smp_defconfig | 04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
|
| /openbmc/linux/arch/arc/kernel/ |
| H A D | setup.c | 04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
|
| /openbmc/linux/arch/arc/ |
| H A D | Kconfig | 04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
04421420 Mon Oct 31 16:26:41 CDT 2016 Vineet Gupta <vgupta@synopsys.com> ARC: timer: gfrc, rtc: build under same option (64-bit timers)
The original distinction was done as they were developed at different
times and primarily because they are specific to UP (RTC) and SMP (GFRC).
But given that driver handles that at runtime, (i.e. not allowing
RTC as clocksource in SMP), we can simplify things a bit.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
|