Re: [beagleboard] Etnaviv drm driver for AM57x GC320
On 11/17/2016 10:45 AM, Robert Nelson wrote: This is awesome Julien!!! 2d is s much smoother... debian@beaglebone:~$ uname -r ; dmesg | grep etnaviv 4.4.32-ti-r68 [ 10.101371] etnaviv gpu-subsystem: bound 5900.bb2d (ops gpu_ops [etnaviv]) [ 10.101392] etnaviv-gpu 5900.bb2d: model: GC320, revision: 5301 Here's my current step-by-step https://gist.github.com/RobertCNelson/fc6d07157b0fcc13b9c28c5832fdc74b I'll start packing those git repo's so that this sunday we'll have 2d acceleration out of the box!! Regards, I am curious to know if there are plans of sending the kernel patches upstream to k.org (if not already there) dumb question: What about the userspace - is this from some variant of official repository? -- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/2d966a08-1719-6e7a-78bb-005dab2a10c7%40ti.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)
Emanuel, On 11/12/2014 03:43 PM, Emmanuel Fusté wrote: Le 12/11/2014 19:54, menon.nisha...@gmail.com a écrit : On Wed, Nov 12, 2014 at 12:52 PM, John Syn wrote: From: Emmanuel Fusté Reply-To: "beagleboard@googlegroups.com" Date: Monday, November 10, 2014 at 12:29 PM To: "beagleboard@googlegroups.com" Subject: Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :) Look at the recently submited mail box subsystem. Please share a link http://marc.info/?l=linux-omap&w=2&r=1&s=mailbox&q=b Yes thank you, I did not saw my mail reaching the mailing list. The recently merged generic mailbox subsystem and the omap mailbox driver are the foundations for remoteproc. All in on the way. This is a big step forward for all past and future ti soc. http://marc.info/?l=linux-omap&m=141505601225611&w=2 Posted on mailing is just step #1. here are other steps needed: - Device Tree maintainers need to ack - that takes a bunch of time and sometimes depends on the polarity of solar flares and grace of a bunch of overworked devicetree maintainers dragged in all directions. - Mailbox maintainer need to ack as well - which means the mailbox and rproc framework cannot conflict against other SoCs.. - All of these must finally be accepted by Linus. Just coz it is posted around 3.18-rc4 requesting dt reviewers indicates it probably will miss 3.19 window, 3.20-rc1 is the next opportunity (umm 5 months away)? yeah - it will be nice to get additional review help on the linux-omap mailing list so that maintainer jobs are a little easier.. all contributions welcome. we will continue to push from our side ofcourse.. but kernel.org support takes time... --- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Recommendation to boot / resume Linux in less than a second...
On 11/12/2014 01:10 PM, John Syn wrote: Q: Have you guys ever tried reducing boot-times through a hibernate-based solution? (e.g. Warp) How do these stackup versus efforts to fast-boot Linux as detailed in this thread? This won’t work at this time: http://www.spinics.net/lists/linux-omap/msg109331.html Just to be clear: DS0 and suspend to ram is not the same as traditional hibernation -> hibernation tends to be suspend-to-disk(ish) complete snapshot of the system. We are not attempting to do that as part of Dave's series and target in upstream. (it might eventually facilitate a similar solution with tux-on-ice or something in that line...) - but not yet. Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)
On 11/07/2014 03:43 PM, Nishanth Menon wrote: On Fri, Nov 7, 2014 at 3:40 PM, Laurent Desnogues wrote: On Fri, Nov 7, 2014 at 7:32 PM, Gerald Coley wrote: Definitely not one of those. Look at what it has on it and make a good guess. You got me wondering because Richard basically copied his info from Nishanth Menon himself: https://patchwork.kernel.org/patch/5245961/ Sigh.. at least use the typo corrected patch V2: https://patchwork.kernel.org/patch/5254791/ :P just in case folks are interested: https://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/commit/?h=omap-for-v3.19/dt&id=80c4955b7ad9daaf34a46f47f7cb556ef2728af7 queued for 3.19-rc1 -- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)
On Mon, Nov 10, 2014 at 3:18 PM, John Syn wrote: > > On 11/10/14, 1:06 PM, "Suman Anna" wrote: > >>Hi John, >> >>On 11/10/2014 02:24 PM, John Syn wrote: >>> >>> On 11/10/14, 10:58 AM, "Nishanth Menon" wrote: >>> >>>> On Mon, Nov 10, 2014 at 11:54 AM, John Syn wrote: >>>>> >>>>> On 11/10/14, 1:15 AM, "Jason Kridner" >>>>>wrote: >>>>> >>>>>> On Sun, Nov 9, 2014 at 1:13 AM, Maxim Podbereznyy >>>>>> >>>>>> wrote: >>>>>>> John Syn, >>>>>>> Wandboard Quad does have 64 bit memory bus. >>>>>>> >>>>>>> P.S. I don't know who needs dual DSP onboard because TI definitely >>>>>>> will >>>>>>> not >>>>>>> support them as should like it was for omap3/dm37. I'd better have >>>>>>> well >>>>>>> supported hardware video encoder/decoder rather than double general >>>>>>> purpose >>>>>>> DSPs without any software support >>>>>> >>>>>> When OMAP3 came out, the only compilers for C6000 were expensive, >>>>>> closed-source compilers. Now, there is support in mainline GCC for >>>>>> C6000. As the BeagleBoard.org community, we have to work together to >>>>>> enable use of the DSPs if they are of interest to the >>>>>> community---there aren't any barriers in our way. >>>>> The TI C6000 does some amazing pipeline optimization, which seems to >>>>>be >>>>> missing from the GCC compiler. Anyway, using CCSV6 is no big deal, but >> >>One should be able to directly download the C6000 compilers at >>http://software-dl.ti.com/codegen/non-esd/downloads/download.htm#C6000 >> >>>>> support for RPMSG/REMOTEPROC on this processor is a big issue. The >>>>> source >>>>> is difficult to follow and my guess is we would need input from the >>>>> original authors to do this work. >>>> >>>> Why dont we get involved in linux-omap discussions on the topic? most >>>> of the rpmsg and remote proc discussions do take place in kernel >>>> mailing list. usually discussing in context helps move patches forward >>>> since it makes it clear to certain maintainers that these things are >>>> important and help community. >>>> >>>> >>>> Do you have anything specific that you are concerned about? >> >>> Looking at git.ti.com/rpmsg/rpmsg, I don¹t see any support for AM572x >>> processors. Also, Beagleboard-X15 is to be released with Kernel V3.18 >>>but >>> I don¹t see support for this kernel versions. Last I heard, RPMSG was >>> working on OMAP4, but not fully implemented on OMAP5, but this was a >>>while >>> ago and perhaps this has changed. Perhaps Suman can give us an update. >>> Similar concerns about REMOTEPROC. What I know is that I have been >>>pushing >>> this issue on the beta list and the only feedback I received was that >>> "RPMSG/REMOTEPROC was in a SW blackhole². >> >>The rpmsg-ti-linux-3.14.y branch in the above tree is the feature >>integration branch for rpmsg/remoteproc and does support all the >>processors on OMAP4, OMAP5 and AM572x/DRA7x. The AM572x support should >>be present through the am57xx-beagle-x15.dts file (its been sometime >>since I pulled the required platform branch with any updates to this). >> >>I am in the process of pushing all these features/patches upstream, but >>it will mostly be sometime next year before all the patches and their >>dependencies will make it into the upstream kernel, so until then have >>to rely on a TI tree. > Hi Suman, > > That is really good news. I’m guessing that V3.18 support will occur with > the push to mainline? Any chance that we will see support when > Beagleboard-X15 launches in Feb 2015? > > Regards, > John >> >>regards >>Suman >> >>> >>> Based on the TRM, this processor looks extremely attractive, and we need >>> RPMSG/REMOTEPROC to take advantage of the powerful dual DSPs and dual >>> CortexM4s. >>> Fixing up linux-omap mailing list -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)
On Mon, Nov 10, 2014 at 11:54 AM, John Syn wrote: > > On 11/10/14, 1:15 AM, "Jason Kridner" wrote: > >>On Sun, Nov 9, 2014 at 1:13 AM, Maxim Podbereznyy >>wrote: >>> John Syn, >>> Wandboard Quad does have 64 bit memory bus. >>> >>> P.S. I don't know who needs dual DSP onboard because TI definitely will >>>not >>> support them as should like it was for omap3/dm37. I'd better have well >>> supported hardware video encoder/decoder rather than double general >>>purpose >>> DSPs without any software support >> >>When OMAP3 came out, the only compilers for C6000 were expensive, >>closed-source compilers. Now, there is support in mainline GCC for >>C6000. As the BeagleBoard.org community, we have to work together to >>enable use of the DSPs if they are of interest to the >>community---there aren't any barriers in our way. > The TI C6000 does some amazing pipeline optimization, which seems to be > missing from the GCC compiler. Anyway, using CCSV6 is no big deal, but > support for RPMSG/REMOTEPROC on this processor is a big issue. The source > is difficult to follow and my guess is we would need input from the > original authors to do this work. Why dont we get involved in linux-omap discussions on the topic? most of the rpmsg and remote proc discussions do take place in kernel mailing list. usually discussing in context helps move patches forward since it makes it clear to certain maintainers that these things are important and help community. Do you have anything specific that you are concerned about? -- --- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)
On Fri, Nov 7, 2014 at 3:40 PM, Laurent Desnogues wrote: > On Fri, Nov 7, 2014 at 7:32 PM, Gerald Coley wrote: >> Definitely not one of those. Look at what it has on it and make a good >> guess. > > You got me wondering because Richard basically copied his info > from Nishanth Menon himself: > > https://patchwork.kernel.org/patch/5245961/ > Sigh.. at least use the typo corrected patch V2: https://patchwork.kernel.org/patch/5254791/ :P -- Regards, NM -- --- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] [PATCH POST V2] ARM: dts: Add am57xx-beagle-x15
BeagleBoard-X15 is the next generation Open Source Hardware
BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHz A15
processor. The platform features 2GB DDR3L (w/dual 32bit busses),
eSATA, 3 USB3.0 ports, integrated HDMI (1920x1080@60), separate LCD
port, video In port, 4GB eMMC, uSD, Analog audio in/out, dual 1G
Ethernet.
For more information, refer to:
BeagleBoard-X15 Wiki:
http://www.elinux.org/Beagleboard:BeagleBoard-X15
AM5728 is part of the Sitara product family whose additional details
will be available: http://www.ti.com/lsds/ti/arm/overview.page
Technical Reference Manual for AM5728 is public domain at:
http://www.ti.com/lit/spruhz6
Just add basic support for the moment, the following updates are needed:
i)Ethernet - depends on SoC dts fixes
ii) USB Client (USB2) - depends on GPIO extcon
ii) HDMI - additional driver fixes pending
iii) Audio - additional driver fixes pending
NOTE:
AM5728 Data Manual (SPRS915L - August 2014) section 4.1.1 states: "All
unused power supply balls must be supplied with the voltages specified
in the Section 5.2, Recommended Operating Conditions". This implies
that all unused voltage rails for AM5728 can never be switched off even
if the hardware blocks inside that voltage domain is unused. Switching
off these unused rails may result in stability issues on other domains
and increased leakage and power-on-hour impacts.
Signed-off-by: Felipe Balbi
Signed-off-by: Nishanth Menon
---
Changes in V2 since V1:
(was updated since v2 inline was posted
https://patchwork.kernel.org/patch/5245961/ )
- Fix the missing squash of proper DDR size.
- Update commit message on why VDD rails must be always-on
- Fix commit message typos (thanks to G+ review :P )
- Explicit palmas sub irq level in dts (it is not configurable,
but better to be properly documented)
V1: https://patchwork.kernel.org/patch/5244801/
Additional references:
- Missing ethernet dtsi patch series:
http://marc.info/?t=14138858531&r=1&w=2
- Missing USB Client extcon patch series:
http://marc.info/?t=14152016084&r=1&w=2
Tested with omap2plus_defconfig modified as: http://slexy.org/view/s2DRTzUwjj
boot log: http://slexy.org/raw/s25Grf1uoo
based on 3.18-rc1 tag.
Support for u-boot has been posted as well: (series ending
http://patchwork.ozlabs.org/patch/407552/ )
Side note: this patch generates a few unrelated checkpatch warning for
compatible which probably is part of appropriate driver documentation
fixes (functionality is already present).
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/am57xx-beagle-x15.dts | 405 +++
2 files changed, 406 insertions(+)
create mode 100644 arch/arm/boot/dts/am57xx-beagle-x15.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 38c89ca..eee1e4f 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -347,6 +347,7 @@ dtb-$(CONFIG_SOC_OMAP5) += omap5-cm-t54.dtb \
omap5-sbc-t54.dtb \
omap5-uevm.dtb
dtb-$(CONFIG_SOC_DRA7XX) += dra7-evm.dtb \
+ am57xx-beagle-x15.dtb \
dra72-evm.dtb
dtb-$(CONFIG_ARCH_ORION5X) += orion5x-lacie-d2-network.dtb \
orion5x-lacie-ethernet-disk-mini-v2.dtb \
diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts
b/arch/arm/boot/dts/am57xx-beagle-x15.dts
new file mode 100644
index 000..49edbda
--- /dev/null
+++ b/arch/arm/boot/dts/am57xx-beagle-x15.dts
@@ -0,0 +1,405 @@
+/*
+ * Copyright (C) 2014 Texas Instruments Incorporated - http://www.ti.com/
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+/dts-v1/;
+
+#include "dra74x.dtsi"
+#include
+#include
+#include
+
+/ {
+ model = "TI AM5728 BeagleBoard-X15";
+ compatible = "ti,am572x-beagle-x15", "ti,am5728", "ti,dra742",
"ti,dra74", "ti,dra7";
+
+ aliases {
+ rtc0 = &mcp_rtc;
+ rtc1 = &tps659038_rtc;
+ };
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x8000>;
+ };
+
+ vdd_3v3: fixedregulator-vdd_3v3 {
+ compatible = "regulator-fixed";
+ regulator-name = "vdd_3v3";
+ vin-supply = <®en1>;
+ regulator-min-microvolt = <330>;
+ regulator-max-microvolt = <330>;
+ };
+
+ vtt_fixed: fixedregulator-vtt {
+ /* TPS51200 */
+ compatible = "regulator-fixed";
+ regulator-name = "vtt_fixed";
+ vin-supply = <&smps3_reg>;
+ regulator-min-microvolt = <330&
[beagleboard] Re: [PATCH] ARM: dts: Add am57xx-beagle-x15
On 10:53-20141106, Nishanth Menon wrote: > On 11/06/2014 10:48 AM, Tony Lindgren wrote: > > * Nishanth Menon [141106 08:44]: > >> On 11/06/2014 10:37 AM, Tom Rini wrote: > >> > >>>>> device_type = "memory"; + reg = <0x8000 0x4000>; > >>>>> /* 1GB > >>>>> to start. Target 2GB */ > >>>> > >>>> 1GiB ? Why would you put this here btw ? u-boot fills this one up. > >>> > >>> Yes, it should either be the full and correct value or 0x0 (like a > >>> number of PowerPC platforms do) so it's clear something else gives us > >>> the right value here. > >> > >> Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i > >> will repost with proper 2GB. it is better that way in case being used > >> with "other bootloaders" which are not exactly too good like u-boot. > > > > Can you also describe why all the always-on regulators are needed? > yep - will do that similar to > https://patchwork.kernel.org/patch/5125431/ - same rationale unless > there is any specific voltage rail that you are explicitly interested > in that needs additional explanation. Is there additional rails of > interest? Here is what I have in mind: (updated with comments from Felipe/Tom and above) - would you like more details added - if you could point out areas of interest, I can help improve information provided here. 8<--- >From d73029bc01c9e2193fb769ce5cc6cc5abb14eba5 Mon Sep 17 00:00:00 2001 From: Nishanth Menon Date: Mon, 18 Aug 2014 12:14:08 -0500 Subject: [PATCH V2] ARM: dts: Add am57xx-beagle-x15 BeagleBoard-X15 is the next generation Open Source Hardware BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHZ A15 processor. The platform features 2GB DDR3L (w/dual 32bit busses), eSATA, 3 USB3.0 ports, integrated HDMI (1920x108@60), separate LCD port, video In port, 4GB eMMC, uSD, Analog audio in/out, dual 1G Ethernet. For more information, refer to: BeagleBoard-X15 Wiki: http://www.elinux.org/Beagleboard:BeagleBoard-X15 AM5728 is part of the Sitara product family whose additional details will be available: http://www.ti.com/lsds/ti/arm/overview.page Technical Reference Manual for AM5728 is public domain at: http://www.ti.com/lit/spruhz6 Just add basic support for the moment, the following updates are needed: i)Ethernet - depends on SoC dts fixes ii) USB Client (USB2) - depends on GPIO extcon ii) HDMI - additional driver fixes pending iii) Audio - additional driver fixes pending NOTE: AM5728 Data Manual (SPRS915L - August 2014) section 4.1.1 states: "All unused power supply balls must be supplied with the voltages specified in the Section 5.2, Recommended Operating Conditions". This implies that all unused voltage rails for AM5728 can never be switched off even if the hardware blocks inside that voltage domain is unused. Switching off these unused rails may result in stability issues on other domains and increased leakage and power-on-hour impacts. Signed-off-by: Felipe Balbi Signed-off-by: Nishanth Menon --- Changes in V2 since V1: - Fix the missing squash of proper DDR size. V1: https://patchwork.kernel.org/patch/5244801/ Additional references: - Missing ethernet dtsi patch series: http://marc.info/?t=14138858531&r=1&w=2 - Missing USB Client extcon patch series: http://marc.info/?t=14152016084&r=1&w=2 Tested with omap2plus_defconfig modified as: http://slexy.org/view/s2DRTzUwjj boot log: http://slexy.org/raw/s25Grf1uoo based on 3.18-rc1 tag. Support for u-boot has been posted as well: (series ending http://patchwork.ozlabs.org/patch/407552/ ) Side note: this patch generates a few unrelated checkpatch warning for compatible which probably is part of appropriate driver documentation fixes (functionality is already present). arch/arm/boot/dts/Makefile |1 + arch/arm/boot/dts/am57xx-beagle-x15.dts | 405 +++ 2 files changed, 406 insertions(+) create mode 100644 arch/arm/boot/dts/am57xx-beagle-x15.dts diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile index 38c89ca..eee1e4f 100644 --- a/arch/arm/boot/dts/Makefile +++ b/arch/arm/boot/dts/Makefile @@ -347,6 +347,7 @@ dtb-$(CONFIG_SOC_OMAP5) += omap5-cm-t54.dtb \ omap5-sbc-t54.dtb \ omap5-uevm.dtb dtb-$(CONFIG_SOC_DRA7XX) += dra7-evm.dtb \ + am57xx-beagle-x15.dtb \ dra72-evm.dtb dtb-$(CONFIG_ARCH_ORION5X) += orion5x-lacie-d2-network.dtb \ orion5x-lacie-ethernet-disk-mini-v2.dtb \ diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts b/arch/arm/boot/dts/am57xx-beagle-x15.dts new file mode 100644 index 000..1f1875b --- /dev/null +++ b/arch/arm/boot/dts/am57xx-beagle-x15.dts @@ -0,0 +1,405
[beagleboard] Re: [PATCH] ARM: dts: Add am57xx-beagle-x15
On 11/06/2014 10:48 AM, Tony Lindgren wrote: > * Nishanth Menon [141106 08:44]: >> On 11/06/2014 10:37 AM, Tom Rini wrote: >> >>>>> device_type = "memory"; + reg = <0x8000 0x4000>; /* 1GB >>>>> to start. Target 2GB */ >>>> >>>> 1GiB ? Why would you put this here btw ? u-boot fills this one up. >>> >>> Yes, it should either be the full and correct value or 0x0 (like a >>> number of PowerPC platforms do) so it's clear something else gives us >>> the right value here. >> >> Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i >> will repost with proper 2GB. it is better that way in case being used >> with "other bootloaders" which are not exactly too good like u-boot. > > Can you also describe why all the always-on regulators are needed? yep - will do that similar to https://patchwork.kernel.org/patch/5125431/ - same rationale unless there is any specific voltage rail that you are explicitly interested in that needs additional explanation. Is there additional rails of interest? -- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] [PATCH] ARM: dts: Add am57xx-beagle-x15
BeagleBoard-X15 is the next generation Open Source Hardware
BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHZ A15
processor. The platform features 2GB DDR3L (w/dual 32bit busses),
eSATA, 3 USB3.0 ports, integrated HDMI (1920x108@60), separate LCD
port, video In port, 4GB eMMC, uSD, Analog audio in/out, dual 1G
Ethernet.
For more information, refer to:
BeagleBoard-X15 Wiki:
http://www.elinux.org/Beagleboard:BeagleBoard-X15
AM5728 is part of the Sitara product family whose additional details
will be available: http://www.ti.com/lsds/ti/arm/overview.page
Technical Reference Manual for AM5728 is public domain at:
http://www.ti.com/lit/spruhz6
Just add basic support for the moment, the following updates are needed:
i)Ethernet - depends on SoC dts fixes
ii) USB Client (USB2) - depends on GPIO extcon
ii) HDMI - additional driver fixes pending
iii) Audio - additional driver fixes pending
Signed-off-by: Felipe Balbi
Signed-off-by: Nishanth Menon
---
Tested with omap2plus_defconfig modified as: http://slexy.org/view/s2DRTzUwjj
boot log: http://slexy.org/raw/s25Grf1uoo
based on 3.18-rc1 tag.
Support for u-boot has been posted as well: (series ending
http://patchwork.ozlabs.org/patch/407552/ )
Side note: this patch generates a few unrelated checkpatch warning for
compatible which probably is part of appropriate driver documentation
fixes (functionality is already present).
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/am57xx-beagle-x15.dts | 405 +++
2 files changed, 406 insertions(+)
create mode 100644 arch/arm/boot/dts/am57xx-beagle-x15.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 38c89ca..eee1e4f 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -347,6 +347,7 @@ dtb-$(CONFIG_SOC_OMAP5) += omap5-cm-t54.dtb \
omap5-sbc-t54.dtb \
omap5-uevm.dtb
dtb-$(CONFIG_SOC_DRA7XX) += dra7-evm.dtb \
+ am57xx-beagle-x15.dtb \
dra72-evm.dtb
dtb-$(CONFIG_ARCH_ORION5X) += orion5x-lacie-d2-network.dtb \
orion5x-lacie-ethernet-disk-mini-v2.dtb \
diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts
b/arch/arm/boot/dts/am57xx-beagle-x15.dts
new file mode 100644
index 000..1f1875b
--- /dev/null
+++ b/arch/arm/boot/dts/am57xx-beagle-x15.dts
@@ -0,0 +1,405 @@
+/*
+ * Copyright (C) 2014 Texas Instruments Incorporated - http://www.ti.com/
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+/dts-v1/;
+
+#include "dra74x.dtsi"
+#include
+#include
+#include
+
+/ {
+ model = "TI AM5728 BeagleBoard-X15";
+ compatible = "ti,am572x-beagle-x15", "ti,am5728", "ti,dra742",
"ti,dra74", "ti,dra7";
+
+ aliases {
+ rtc0 = &mcp_rtc;
+ rtc1 = &tps659038_rtc;
+ };
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x4000>; /* 1GB to start. Target 2GB */
+ };
+
+ vdd_3v3: fixedregulator-vdd_3v3 {
+ compatible = "regulator-fixed";
+ regulator-name = "vdd_3v3";
+ vin-supply = <®en1>;
+ regulator-min-microvolt = <330>;
+ regulator-max-microvolt = <330>;
+ };
+
+ vtt_fixed: fixedregulator-vtt {
+ /* TPS51200 */
+ compatible = "regulator-fixed";
+ regulator-name = "vtt_fixed";
+ vin-supply = <&smps3_reg>;
+ regulator-min-microvolt = <330>;
+ regulator-max-microvolt = <330>;
+ regulator-always-on;
+ regulator-boot-on;
+ enable-active-high;
+ gpio = <&gpio7 11 GPIO_ACTIVE_HIGH>;
+ };
+
+ leds {
+ compatible = "gpio-leds";
+ pinctrl-names = "default";
+ pinctrl-0 = <&leds_pins_default>;
+
+ led@0 {
+ label = "beagle-x15:usr0";
+ gpios = <&gpio7 9 GPIO_ACTIVE_HIGH>;
+ linux,default-trigger = "heartbeat";
+ default-state = "off";
+ };
+
+ led@1 {
+ label = "beagle-x15:usr1";
+ gpios = <&gpio7 8 GPIO_ACTIVE_HIGH>;
+ linux,default-trigger = "cpu0";
+ default-state = "off";
+ };
+
+ led@2 {
+ label = "beagle-x15:usr2";
+ gpios = <&gp
[beagleboard] Re: [PATCH] ARM: dts: Add am57xx-beagle-x15
On 11/06/2014 10:37 AM, Tom Rini wrote: >>> device_type = "memory"; + reg = <0x8000 0x4000>; /* 1GB >>> to start. Target 2GB */ >> >> 1GiB ? Why would you put this here btw ? u-boot fills this one up. > > Yes, it should either be the full and correct value or 0x0 (like a > number of PowerPC platforms do) so it's clear something else gives us > the right value here. Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i will repost with proper 2GB. it is better that way in case being used with "other bootloaders" which are not exactly too good like u-boot. -- Regards, Nishanth Menon -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
