From: Jon Mason <hidden> Date: 2015-10-02 22:22:50
Add device tree files for Broadcom Northstar based SVKs. Since the
bcm5301x.dtsi already exists, all that is necessary is the dts files to
enable the UARTs (and specify the RAM size for the 4708/9). With these
files, the SVKs are able to boot to shell.
Signed-off-by: Jon Mason <redacted>
---
arch/arm/boot/dts/Makefile | 5 +++-
arch/arm/boot/dts/bcm94708.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm94709.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm953012k.dts | 59 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 167 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/bcm94708.dts
create mode 100644 arch/arm/boot/dts/bcm94709.dts
create mode 100644 arch/arm/boot/dts/bcm953012k.dts
From: Jon Mason <hidden> Date: 2015-10-02 22:22:51
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
Add device tree files for Broadcom Northstar based SVKs. Since the
bcm5301x.dtsi already exists, all that is necessary is the dts files to
enable the UARTs (and specify the RAM size for the 4708/9). With these
files, the SVKs are able to boot to shell.
Signed-off-by: Jon Mason <redacted>
---
arch/arm/boot/dts/Makefile | 5 +++-
arch/arm/boot/dts/bcm94708.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm94709.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm953012k.dts | 59 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 167 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/bcm94708.dts
create mode 100644 arch/arm/boot/dts/bcm94709.dts
create mode 100644 arch/arm/boot/dts/bcm953012k.dts
Currently the files are named beginning with the chip name something
like this should fit better the other naming schema:
arch/arm/boot/dts/bcm4708-brcm-bcm94708.dts
quoted hunk
@@ -0,0 +1,52 @@+/*+ * BSD LICENSE+ *+ * Copyright(c) 2015 Broadcom Corporation. All rights reserved.+ *+ * Redistribution and use in source and binary forms, with or without+ * modification, are permitted provided that the following conditions+ * are met:+ *+ * * Redistributions of source code must retain the above copyright+ * notice, this list of conditions and the following disclaimer.+ * * Redistributions in binary form must reproduce the above copyright+ * notice, this list of conditions and the following disclaimer in+ * the documentation and/or other materials provided with the+ * distribution.+ * * Neither the name of Broadcom Corporation nor the names of its+ * contributors may be used to endorse or promote products derived+ * from this software without specific prior written permission.+ *+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS+ * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT+ * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR+ * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT+ * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.+ */++/dts-v1/;++#include "bcm5301x.dtsi"++/ {+ model = "NorthStar SVK (BCM94708)";+ compatible = "brcm,bcm4708";
The compatible string should also contain this exactly board like this:
compatible = "brcm,bcm94708", "brcm,bcm4708";
Instead of using mem=128M you should add an extra node like this:
memory {
reg = <0x00000000 0x08000000>;
};
Does this board only has 128M of RAM? currently we restrict all of them
to that, but I just want to know.
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
What should be documented in this file? This is more a question to the
guys more familiar with arm in Linux. Currently the Linux kernel only
supports brcm,bcm4708 and all goes back to that one.
quoted hunk
@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties: Required root node property:+bcm94709 compatible = "brcm,bcm4708";++bcm94709+compatible = "brcm,bcm4709", "brcm,bcm4708";++bcm953012k+compatible = "brcm,bcm5301k", "brcm,bcm4708";
From: Scott Branden <sbranden@broadcom.com> Date: 2015-10-13 16:58:29
Hi Jon,
One question below.
On 15-10-10 07:42 AM, Hauke Mehrtens wrote:
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
What should be documented in this file? This is more a question to the
guys more familiar with arm in Linux. Currently the Linux kernel only
supports brcm,bcm4708 and all goes back to that one.
quoted
@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties: Required root node property:+bcm94709 compatible = "brcm,bcm4708";++bcm94709+compatible = "brcm,bcm4709", "brcm,bcm4708";++bcm953012k+compatible = "brcm,bcm5301k", "brcm,bcm4708";
Why are you adding a "k" on the string here? bcm5301k is not an SoC
part number?
From: Jon Mason <hidden> Date: 2015-10-13 21:38:24
On Sat, Oct 10, 2015 at 04:39:00PM +0200, Hauke Mehrtens wrote:
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add device tree files for Broadcom Northstar based SVKs. Since the
bcm5301x.dtsi already exists, all that is necessary is the dts files to
enable the UARTs (and specify the RAM size for the 4708/9). With these
files, the SVKs are able to boot to shell.
Signed-off-by: Jon Mason <redacted>
---
arch/arm/boot/dts/Makefile | 5 +++-
arch/arm/boot/dts/bcm94708.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm94709.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm953012k.dts | 59 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 167 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/bcm94708.dts
create mode 100644 arch/arm/boot/dts/bcm94709.dts
create mode 100644 arch/arm/boot/dts/bcm953012k.dts
Currently the files are named beginning with the chip name something
like this should fit better the other naming schema:
arch/arm/boot/dts/bcm4708-brcm-bcm94708.dts
Sorry, I was following the namign schema that we've been using on
other Broadcom SVKs in the Linux device tree directory. For example,
arch/arm/boot/dts/bcm911360_entphn.dts
arch/arm/boot/dts/bcm911360k.dts
arch/arm/boot/dts/bcm958300k.dts
arch/arm/boot/dts/bcm958305k.dts
arch/arm/boot/dts/bcm958625k.dts
arch/arm/boot/dts/bcm963138dvt.dts
Also, this is the name we have been using internally. So, it will
making migrating to newer kernels much easier.
quoted
@@ -0,0 +1,52 @@+/*+ * BSD LICENSE+ *+ * Copyright(c) 2015 Broadcom Corporation. All rights reserved.+ *+ * Redistribution and use in source and binary forms, with or without+ * modification, are permitted provided that the following conditions+ * are met:+ *+ * * Redistributions of source code must retain the above copyright+ * notice, this list of conditions and the following disclaimer.+ * * Redistributions in binary form must reproduce the above copyright+ * notice, this list of conditions and the following disclaimer in+ * the documentation and/or other materials provided with the+ * distribution.+ * * Neither the name of Broadcom Corporation nor the names of its+ * contributors may be used to endorse or promote products derived+ * from this software without specific prior written permission.+ *+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS+ * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT+ * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR+ * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT+ * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.+ */++/dts-v1/;++#include "bcm5301x.dtsi"++/ {+ model = "NorthStar SVK (BCM94708)";+ compatible = "brcm,bcm4708";
The compatible string should also contain this exactly board like this:
compatible = "brcm,bcm94708", "brcm,bcm4708";
Instead of using mem=128M you should add an extra node like this:
memory {
reg = <0x00000000 0x08000000>;
};
Does this board only has 128M of RAM? currently we restrict all of them
to that, but I just want to know.
The 4708/9 SVKs have 128M, but the 53012 has 256M.
It seems to me that this who 4708 base is kind of a misnomer. They
really are "Northstar". Would it not be more accurate to change it to
be
compatible = "brcm,bcm4709", "brcm,ns";
?
Just out of curiosity on what does this clock frequency depend? I saw
your patch adding a real clock driver which should make this obsolete.
Better to add this now, as the device tree part might be out of sync
for a time. Also, is it not better to make the UARTs a static clock
and not dependent on the clk driver?
Thanks,
Jon
quoted
+ status = "okay";
+};
+
+&uart1 {
+ clock-frequency = <62499840>;
+ status = "okay";
+};
From: Jon Mason <hidden> Date: 2015-10-13 21:40:56
On Sat, Oct 10, 2015 at 04:42:04PM +0200, Hauke Mehrtens wrote:
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
What should be documented in this file? This is more a question to the
guys more familiar with arm in Linux. Currently the Linux kernel only
supports brcm,bcm4708 and all goes back to that one.
I was under the impression that all boards should be added to these
files. We have been doing so for Cygnus and NSP.
Thanks,
Jon
quoted
@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties: Required root node property:+bcm94709 compatible = "brcm,bcm4708";++bcm94709+compatible = "brcm,bcm4709", "brcm,bcm4708";++bcm953012k+compatible = "brcm,bcm5301k", "brcm,bcm4708";
On Sat, Oct 10, 2015 at 04:42:04PM +0200, Hauke Mehrtens wrote:
quoted
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
What should be documented in this file? This is more a question to the
guys more familiar with arm in Linux. Currently the Linux kernel only
supports brcm,bcm4708 and all goes back to that one.
I was under the impression that all boards should be added to these
files. We have been doing so for Cygnus and NSP.
Tracking exactly which boards are supported by the brcm,bcm4708
compatible string might be tedious, I tend to agree with just listing
the supported SoCs, and leaving the specific board compatibles to the
individual DTS files instead.
Thanks,
Jon
quoted
quoted
@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties: Required root node property:+bcm94709 compatible = "brcm,bcm4708";++bcm94709+compatible = "brcm,bcm4709", "brcm,bcm4708";++bcm953012k+compatible = "brcm,bcm5301k", "brcm,bcm4708";
From: Ray Jui <rjui@broadcom.com> Date: 2015-10-13 22:43:24
On 10/13/2015 2:38 PM, Jon Mason wrote:
On Sat, Oct 10, 2015 at 04:39:00PM +0200, Hauke Mehrtens wrote:
quoted
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add device tree files for Broadcom Northstar based SVKs. Since the
bcm5301x.dtsi already exists, all that is necessary is the dts files to
enable the UARTs (and specify the RAM size for the 4708/9). With these
files, the SVKs are able to boot to shell.
Signed-off-by: Jon Mason <redacted>
---
arch/arm/boot/dts/Makefile | 5 +++-
arch/arm/boot/dts/bcm94708.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm94709.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm953012k.dts | 59 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 167 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/bcm94708.dts
create mode 100644 arch/arm/boot/dts/bcm94709.dts
create mode 100644 arch/arm/boot/dts/bcm953012k.dts
quoted
quoted
+&uart0 {
+ clock-frequency = <62499840>;
Just out of curiosity on what does this clock frequency depend? I saw
your patch adding a real clock driver which should make this obsolete.
Better to add this now, as the device tree part might be out of sync
for a time.
Sure, this can potentially be a reason to not using the real clock node
and just use a hardcoded clock frequency for now, until the other clock
change is merged, then you can submit another patch to use it.
Also, is it not better to make the UARTs a static clock
and not dependent on the clk driver?
I disagree. You should always use the real clock driver for querying the
clock frequency, in the case when the clock driver is available.
Today one can change the core clock for UART in the bootloader for
various reasons (and we saw that happening a lot in the past), which in
this case will make your kernel not seeing any console output.
By always querying the clock rate based on real registers instead of a
hardcoded value, you don't have that issue and your kernel is less
dependent on any changes in the bootloader.
From: Jon Mason <hidden> Date: 2015-10-14 15:34:29
On Tue, Oct 13, 2015 at 03:37:49PM -0700, Florian Fainelli wrote:
On 13/10/15 14:40, Jon Mason wrote:
quoted
On Sat, Oct 10, 2015 at 04:42:04PM +0200, Hauke Mehrtens wrote:
quoted
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
What should be documented in this file? This is more a question to the
guys more familiar with arm in Linux. Currently the Linux kernel only
supports brcm,bcm4708 and all goes back to that one.
I was under the impression that all boards should be added to these
files. We have been doing so for Cygnus and NSP.
Tracking exactly which boards are supported by the brcm,bcm4708
compatible string might be tedious, I tend to agree with just listing
the supported SoCs, and leaving the specific board compatibles to the
individual DTS files instead.
Ok, I'll simply add entries for NS and 4709 to this.
Thanks,
Jon
quoted
Thanks,
Jon
quoted
quoted
@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties: Required root node property:+bcm94709 compatible = "brcm,bcm4708";++bcm94709+compatible = "brcm,bcm4709", "brcm,bcm4708";++bcm953012k+compatible = "brcm,bcm5301k", "brcm,bcm4708";
From: Jon Mason <hidden> Date: 2015-10-14 15:36:52
On Tue, Oct 13, 2015 at 03:43:20PM -0700, Ray Jui wrote:
On 10/13/2015 2:38 PM, Jon Mason wrote:
quoted
On Sat, Oct 10, 2015 at 04:39:00PM +0200, Hauke Mehrtens wrote:
quoted
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add device tree files for Broadcom Northstar based SVKs. Since the
bcm5301x.dtsi already exists, all that is necessary is the dts files to
enable the UARTs (and specify the RAM size for the 4708/9). With these
files, the SVKs are able to boot to shell.
Signed-off-by: Jon Mason <redacted>
---
arch/arm/boot/dts/Makefile | 5 +++-
arch/arm/boot/dts/bcm94708.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm94709.dts | 52 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm953012k.dts | 59 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 167 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/bcm94708.dts
create mode 100644 arch/arm/boot/dts/bcm94709.dts
create mode 100644 arch/arm/boot/dts/bcm953012k.dts
quoted
quoted
quoted
+&uart0 {
+ clock-frequency = <62499840>;
Just out of curiosity on what does this clock frequency depend? I saw
your patch adding a real clock driver which should make this obsolete.
Better to add this now, as the device tree part might be out of sync
for a time.
Sure, this can potentially be a reason to not using the real clock node
and just use a hardcoded clock frequency for now, until the other clock
change is merged, then you can submit another patch to use it.
Also, is it not better to make the UARTs a static clock
quoted
and not dependent on the clk driver?
I disagree. You should always use the real clock driver for querying the
clock frequency, in the case when the clock driver is available.
Today one can change the core clock for UART in the bootloader for
various reasons (and we saw that happening a lot in the past), which in
this case will make your kernel not seeing any console output.
By always querying the clock rate based on real registers instead of a
hardcoded value, you don't have that issue and your kernel is less
dependent on any changes in the bootloader.
Fair enough. This is moot until the clk driver changes get pulled in.
This file can be changed at that time :)
Thanks,
Jon
From: Scott Branden <sbranden@broadcom.com> Date: 2015-10-14 19:44:39
Hi Jon,
Yes, please only add SoC part number compatible strings, not board
compatible strings.
On 15-10-14 08:34 AM, Jon Mason wrote:
On Tue, Oct 13, 2015 at 03:37:49PM -0700, Florian Fainelli wrote:
quoted
On 13/10/15 14:40, Jon Mason wrote:
quoted
On Sat, Oct 10, 2015 at 04:42:04PM +0200, Hauke Mehrtens wrote:
quoted
On 10/03/2015 12:22 AM, Jon Mason wrote:
quoted
Add the 4708, 4709, and 953012k SVKs to the the documentation for the
Broadcom Northstar device tree bindings.
Signed-off-by: Jon Mason <redacted>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
1 file changed, 7 insertions(+)
What should be documented in this file? This is more a question to the
guys more familiar with arm in Linux. Currently the Linux kernel only
supports brcm,bcm4708 and all goes back to that one.
I was under the impression that all boards should be added to these
files. We have been doing so for Cygnus and NSP.
Tracking exactly which boards are supported by the brcm,bcm4708
compatible string might be tedious, I tend to agree with just listing
the supported SoCs, and leaving the specific board compatibles to the
individual DTS files instead.
Ok, I'll simply add entries for NS and 4709 to this.
Good - we have only been adding SoC compatible strings for Cygnus and
NSP - not board compatibles.
Thanks,
Jon
quoted
quoted
Thanks,
Jon
quoted
quoted
@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties: Required root node property:+bcm94709 compatible = "brcm,bcm4708";++bcm94709+compatible = "brcm,bcm4709", "brcm,bcm4708";++bcm953012k+compatible = "brcm,bcm5301k", "brcm,bcm4708";