diff options
author | Christian Lamparter <chunkeey@gmail.com> | 2019-05-18 11:12:30 +0200 |
---|---|---|
committer | Christian Lamparter <chunkeey@gmail.com> | 2019-05-18 17:59:49 +0200 |
commit | 1e52eacc42dd514a0967d2fcd990572565e5296d (patch) | |
tree | 08fe97438bf8b4a85802314b0a9f3a40f9c72ca8 /target/linux/bcm53xx | |
parent | 73e0f52b6e4e1c79e4e95573f2050ae9ff10ac00 (diff) | |
download | upstream-1e52eacc42dd514a0967d2fcd990572565e5296d.tar.gz upstream-1e52eacc42dd514a0967d2fcd990572565e5296d.tar.bz2 upstream-1e52eacc42dd514a0967d2fcd990572565e5296d.zip |
ath79: use the qca,qca9563 chip compatible for the WR818
All other QCA9563 devices already use this identifier for
the exact SoC. Not that this matters much since as upstream
states in Documentation/devicetree/usage-model.txt:
"First and foremost, the kernel will use data in the DT to
identify the specific machine. In a perfect world, the
specific platform shouldn't matter to the kernel because all
platform details would be described perfectly by the device
tree in a consistent and reliable manner.
[...]
In the majority of cases, the machine identity is irrelevant,
and the kernel will instead select setup code based on the
machine's core CPU or SoC."
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux/bcm53xx')
0 files changed, 0 insertions, 0 deletions