Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/2] OMAP3: update omap_chip flags; mark USBTLL SAR for ES3.1 only
Date: Thu, 29 Jan 2009 02:12:03 -0700	[thread overview]
Message-ID: <20090129090821.24256.46439.stgit@localhost.localdomain> (raw)

Hello,

this series marks USBTLL SAR as being available on ES3.1 and beyond only, 
per 

   http://marc.info/?l=linux-arm-kernel&m=123319614808833&w=2

To do this, the omap_chip flags had to be updated.  Now, ES2+ features
are marked as CHIP_GE_OMAP3430ES2.  ES3.1+ features are similarly marked
as CHIP_GE_OMAP3430ES3_1.

Tested on ES2.1 Beagle.  Further testing on ES3+ boards is very welcome.

---

Paul Walmsley (2):
      OMAP3 powerdomains: make USBTLL SAR only available on ES3.1 and beyond
      OMAP3: update ES level flags to discriminate between post-ES2 revisions


 arch/arm/mach-omap2/clockdomains.h     |    6 +++---
 arch/arm/mach-omap2/id.c               |    7 ++++++-
 arch/arm/mach-omap2/powerdomains.h     |    4 ++--
 arch/arm/mach-omap2/powerdomains34xx.h |   16 +++++++++-------
 arch/arm/plat-omap/include/mach/cpu.h  |   26 ++++++++++++++++++++------
 5 files changed, 40 insertions(+), 19 deletions(-)



             reply	other threads:[~2009-01-29  9:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  9:12 Paul Walmsley [this message]
2009-01-29  9:12 ` [PATCH 1/2] OMAP3: update ES level flags to discriminate between post-ES2 revisions Paul Walmsley
2009-01-29  9:12 ` [PATCH 2/2] OMAP3 powerdomains: make USBTLL SAR only available on ES3.1 and beyond Paul Walmsley

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=20090129090821.24256.46439.stgit@localhost.localdomain \
    --to=paul@pwsan.com \
    --cc=linux-omap@vger.kernel.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