[PATCH v8 0/7] arm: Add basic support for Mediatek Cortex-A7 SoCs
From: Matthias Brugger
Date: Wed Jun 11 2014 - 08:36:55 EST
Eighth round for the Mediatek basic support patches.
The biggest change are the DTS definition of the clocks.
---
This patch set adds basic support for the Mediatek Cortex-A7 SoCs.
Support is quite basic, as the only component working up to now are the
timers.
The patch series is build against torvalds/master tree.
Signed-off-by: Matthias Brugger <matthias.bgg@xxxxxxxxx>
Changes for v8:
1. OF address
- fix style issue
2. clocksource driver
- fix style issue
3. Basic SoC support
- define the clock node as a simple-bus
- delete unused clock-ranges
Changes for v7:
1. OF address
- add of_io_request_and_map
2. Clocksource timer
- use pr_warnings and error handling instead of panic
- fix macro parentheses
- use of_io_request_and_map
3. Others
- rename SoC DT bindings to mediatek.txt
- fixed typos
Changes for v6:
- fix compatible string of the timer
- encapsulate timer setup in function
- add more information to the timer commit message
- add address in timer DTS bindings documentation
Changes for v5:
1. Clocksource timer
- Change the compatible string to mt6577
2. Timer DT bindings
- Change compatible string to mt6577
Changes for v4:
1. Clocksource timer
- use cpu_possible_mask
2. Timer DT bindings
- Delete comments about the frequency of the clocks
- Add clock-names for the input clocks
3. Basic SoC support
- add clock-names for the timer
- rename the label of the clocks nodes
Changes for v3:
1. Clocksource timer
- Set cpu_mask_all and irq in clock_event_device
- Use device private structure for driver specific values
2. Timer DT bindings
- Define order of the clock phandles
- Fix typos
3. Basic SoC support
- DTS: set gic to a15-gic
- DTS: order by physical address
- Remove call to dt_init function
Changes for v2:
1. Clocksource timer
- Delete unused parts for sched_clock_source
- Use irq_request instead of setup_irq
- Remove unused SMP parts
- Fix some style issues
- use of_address_to resource and request_mem_region
- delete use of named clock
- select CLKSRC_MMIO in driver Kconfig
2. DT bindings
- delete named clock bindings
3. Basic SoC support
- Clean-up Kconfig
- Add documentation of the SoC compatible property
- DTS: rename SoC file to mt6589.dts
- DTS: Delete not present cache controller
- DTS: Add missing GICv2 properties
- DTS: Change clock names
- DTS: Add Aquaris5 board
4. Add earlyprintk
- patch droped until serial driver is available
5. Add support for Aquaris5 mobile phone
Matthias Brugger (7):
of: Provide function to request and map memory
clocksource: Add support for the Mediatek SoCs
dt-bindings: add mtk-timer bindings
vendor-prefixes: add prefix for Mediaktek Inc.
arm: add basic support for Mediatek MT6589 boards
dt-bindings: add documentation for Mediatek SoC
arm: mediatek: add dts for Aquaris5 mobile phone
Documentation/devicetree/bindings/arm/mediatek.txt | 8 +
.../bindings/timer/mediatek,mtk-timer.txt | 18 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/Kconfig | 2 +
arch/arm/Makefile | 1 +
arch/arm/boot/dts/mt6589-aquaris5.dts | 25 ++
arch/arm/boot/dts/mt6589.dtsi | 94 +++++++
arch/arm/mach-mediatek/Kconfig | 6 +
arch/arm/mach-mediatek/Makefile | 1 +
arch/arm/mach-mediatek/mediatek.c | 27 ++
drivers/clocksource/Kconfig | 5 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/mtk_timer.c | 261 ++++++++++++++++++++
drivers/of/address.c | 29 +++
include/linux/of_address.h | 8 +
15 files changed, 487 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/mediatek.txt
create mode 100644 Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt
create mode 100644 arch/arm/boot/dts/mt6589-aquaris5.dts
create mode 100644 arch/arm/boot/dts/mt6589.dtsi
create mode 100644 arch/arm/mach-mediatek/Kconfig
create mode 100644 arch/arm/mach-mediatek/Makefile
create mode 100644 arch/arm/mach-mediatek/mediatek.c
create mode 100644 drivers/clocksource/mtk_timer.c
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/