public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] ARM: omap3: evm: Add OF_CONTROL support
Date: Tue, 26 Dec 2017 11:14:55 -0500	[thread overview]
Message-ID: <20171226161455.GU7592@bill-the-cat> (raw)
In-Reply-To: <20171226033403.GA23950@ethiopia.woodsts.org>

On Mon, Dec 25, 2017 at 09:34:03PM -0600, Derald D. Woods wrote:
> On Sat, Dec 16, 2017 at 02:14:47PM -0600, Derald D. Woods wrote:
> > This series adds OF_CONTROL support for TMDSEVM{3530,3730} and
> > additionally updates ethaddr setup with smc911x initialization.
> > 
> > Devicetree files are taken from Linux v4.15-rc3. Note that this is the
> > first addition of OMAP34XX devicetree files.
> > 
> > Tested using GCC 7.2.0 [--with-float=hard --with-mode=thumb]
> > 
> > --- 8< -----------------------------------------------------------------
> > U-Boot SPL 2018.01-rc1-00177-g27f9740bcf (Dec 16 2017 - 13:13:10)
> > Trying to boot from MMC1
> > reading u-boot.img
> > reading u-boot.img
> > 
> > 
> > U-Boot 2018.01-rc1-00177-g27f9740bcf (Dec 16 2017 - 13:13:10 -0600)
> > 
> > OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
> > Model: TI OMAP35XX EVM (TMDSEVM3530)
> > OMAP3 EVM board + LPDDR/NAND
> > I2C:   ready
> > DRAM:  256 MiB
> > NAND:  256 MiB
> > MMC:   OMAP SD/MMC: 0
> > Read back SMSC id 0x92200000
> > OMAP die ID: 265a002400000000040365fa1801b01f
> > Net:   smc911x-0
> > starting USB...
> > USB0:   USB EHCI 1.00
> > scanning bus 0 for devices... 1 USB Device(s) found
> > Hit any key to stop autoboot:  0 
> > OMAP3_EVM # echo $stdin;echo $stdout;echo $stderr
> > serial at 4806a000
> > serial at 4806a000
> > serial at 4806a000
> > --- 8< -----------------------------------------------------------------
> > 
> > 
> > Derald D. Woods (3):
> >   ARM: dts: omap3-evm: Add support for TMDSEVM{3530,3730}
> >   ARM: dts: omap3-evm: Enable DM and devicetree for TMDSEVM{3530,3730}
> >   ARM: omap3: evm: Refactor 'board_eth_init'
> > 
> >  arch/arm/dts/Makefile                           |   4 +
> >  arch/arm/dts/omap-gpmc-smsc911x.dtsi            |  55 ++++++
> >  arch/arm/dts/omap3-evm-37xx-u-boot.dtsi         |  29 ++++
> >  arch/arm/dts/omap3-evm-37xx.dts                 | 110 ++++++++++++
> >  arch/arm/dts/omap3-evm-common.dtsi              | 195 +++++++++++++++++++++
> >  arch/arm/dts/omap3-evm-processor-common.dtsi    | 216 ++++++++++++++++++++++++
> >  arch/arm/dts/omap3-evm-u-boot.dtsi              |  29 ++++
> >  arch/arm/dts/omap3-evm.dts                      |  89 ++++++++++
> >  arch/arm/dts/omap3-panel-sharp-ls037v7dw01.dtsi |  73 ++++++++
> >  arch/arm/dts/omap34xx.dtsi                      |  84 +++++++++
> >  arch/arm/mach-omap2/omap3/Kconfig               |   4 +
> >  board/ti/evm/evm.c                              |  24 +--
> >  configs/omap3_evm_defconfig                     |   9 +-
> >  include/configs/omap3_evm.h                     |   2 -
> >  14 files changed, 896 insertions(+), 27 deletions(-)
> >  create mode 100644 arch/arm/dts/omap-gpmc-smsc911x.dtsi
> >  create mode 100644 arch/arm/dts/omap3-evm-37xx-u-boot.dtsi
> >  create mode 100644 arch/arm/dts/omap3-evm-37xx.dts
> >  create mode 100644 arch/arm/dts/omap3-evm-common.dtsi
> >  create mode 100644 arch/arm/dts/omap3-evm-processor-common.dtsi
> >  create mode 100644 arch/arm/dts/omap3-evm-u-boot.dtsi
> >  create mode 100644 arch/arm/dts/omap3-evm.dts
> >  create mode 100644 arch/arm/dts/omap3-panel-sharp-ls037v7dw01.dtsi
> >  create mode 100644 arch/arm/dts/omap34xx.dtsi
> > 
> > -- 
> > 2.15.1
> > 
> 
> Ping. If there is any concern, please let me know and I will make
> corrections. I plan to also update beagleboard and overo to use their
> respective devicetree files. I would like to have these three OMAP34XX
> boards, that I possess, to be near the same level of support. It will
> help me to continue testing OMAP34XX stuff in general.

It's localized enough that it's your call, do you want it in for
v2018.01 or .03?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171226/8cb527bf/attachment.sig>

  reply	other threads:[~2017-12-26 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-16 20:14 [U-Boot] [PATCH 0/3] ARM: omap3: evm: Add OF_CONTROL support Derald D. Woods
2017-12-16 20:14 ` [U-Boot] [PATCH 1/3] ARM: dts: omap3-evm: Add support for TMDSEVM{3530, 3730} Derald D. Woods
2018-01-02  0:47   ` [U-Boot] [U-Boot, " Tom Rini
2017-12-16 20:14 ` [U-Boot] [PATCH 2/3] ARM: dts: omap3-evm: Enable DM and devicetree " Derald D. Woods
2017-12-17  2:36   ` Derald D. Woods
2017-12-27 13:15     ` [U-Boot] [U-Boot, " Tom Rini
2017-12-27 15:22       ` Derald D. Woods
2017-12-27 15:37     ` [U-Boot] [PATCH v3 " Derald D. Woods
2017-12-27 15:40       ` [U-Boot] [PATCH v4 " Derald D. Woods
2018-01-02  0:47         ` [U-Boot] [U-Boot, v4, " Tom Rini
2017-12-16 20:14 ` [U-Boot] [PATCH 3/3] ARM: omap3: evm: Refactor 'board_eth_init' Derald D. Woods
2018-01-02  0:47   ` [U-Boot] [U-Boot, " Tom Rini
2017-12-26  3:34 ` [U-Boot] [PATCH 0/3] ARM: omap3: evm: Add OF_CONTROL support Derald D. Woods
2017-12-26 16:14   ` Tom Rini [this message]
2017-12-26 17:08     ` Derald D. Woods

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=20171226161455.GU7592@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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