From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] arm64: Add DTS support for FSL's LS2085A SoC
Date: Fri, 15 Aug 2014 17:22:58 +0100 [thread overview]
Message-ID: <20140815162258.GC21908@leverpostej> (raw)
In-Reply-To: <7010d864a31e437d9cccebafdb5f50e7@BY2PR0301MB0743.namprd03.prod.outlook.com>
Hi Stuart
> Is the intent to eventually purge the device trees of enable-method/cpu-release-addr
> and have that set by the boot firmware? Or, keep the spin-table method
> around as a least common denominator mechanism and override it when
> necessary? Wondering what the longer term thinking is...
Personally I'd like to see anything that's not a fixed HW property be
omitted in the DTS and injected by the boot firmware. Certainly anything
which is a property of the FW should be injected by that FW.
That would cover:
- Any enable-method property and related properties and/or nodes. This
is heavily dependent on the boot firmware configuration, and can
differ substantially between instances of a given board.
- Most /memreserve/ uses (as these typically protect firmware or
trampoline code).
- Any memory nodes where memory can be dynamically populated on the
board.
- CPU nodes if the presence of said CPUs is dynamically determined.
In the long term I'd like to see DTS get fully decoupled from the
kernel.
Cheers,
Mark.
next prev parent reply other threads:[~2014-08-15 16:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 9:49 [PATCH 0/6] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-15 9:49 ` [PATCH 1/6] Documentation: DT: Add bindings for FSL NS16550A UART Bhupesh Sharma
2014-08-15 10:46 ` Mark Rutland
2014-08-15 14:42 ` [PATCH 1/6] Documentation: DT: Add bindings for FSL NS16550A The UART bhupesh.sharma at freescale.com
2014-08-15 15:03 ` Mark Rutland
2014-08-20 9:08 ` bhupesh.sharma at freescale.com
2014-08-20 11:31 ` Mark Rutland
2014-08-20 12:20 ` bhupesh.sharma at freescale.com
2014-08-15 9:49 ` [PATCH 2/6] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2014-08-15 9:49 ` [PATCH 3/6] Documentation: DT: Add entry for FSL Management Complex Bhupesh Sharma
2014-08-15 11:00 ` Mark Rutland
2014-08-15 13:12 ` Stuart Yoder
2014-08-15 13:35 ` Kumar Gala
2014-08-15 9:49 ` [PATCH 4/6] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-15 10:12 ` Catalin Marinas
2014-08-15 12:53 ` Stuart Yoder
2014-08-15 13:10 ` Catalin Marinas
2014-08-15 14:31 ` bhupesh.sharma at freescale.com
2014-08-15 15:28 ` Catalin Marinas
2014-08-15 15:57 ` Stuart Yoder
2014-08-15 16:22 ` Mark Rutland [this message]
2014-08-15 16:25 ` Catalin Marinas
2014-08-15 16:44 ` Stuart Yoder
2014-08-15 10:23 ` Mark Rutland
2014-08-15 15:21 ` arnab.basu at freescale.com
2014-08-15 15:26 ` Kumar Gala
2014-08-15 15:41 ` Stuart Yoder
2014-08-15 15:43 ` Kumar Gala
2014-08-15 15:49 ` Stuart Yoder
2014-08-15 16:02 ` Catalin Marinas
2014-08-15 15:37 ` Stuart Yoder
2014-08-15 16:12 ` Mark Rutland
2014-08-15 12:13 ` Marc Zyngier
2014-08-15 13:29 ` Kumar Gala
2014-08-15 14:26 ` bhupesh.sharma at freescale.com
2014-08-15 14:40 ` Kumar Gala
2014-08-15 16:19 ` Stuart Yoder
2014-08-15 9:49 ` [PATCH 5/6] arm64: dts/Makefile: Add support for FSL's LS2085A simulator model Bhupesh Sharma
2014-08-15 9:49 ` [PATCH 6/6] arm64: Add support for FSL's LS2085A SoC in Kconfig and defconfig Bhupesh Sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140815162258.GC21908@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox