public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 1/2] i2c: qup: Add device tree bindings information
Date: Thu, 23 Jan 2014 20:50:24 +0100	[thread overview]
Message-ID: <201401232050.25134.arnd@arndb.de> (raw)
In-Reply-To: <174308F1-FFD2-4CB3-AEA2-C423F90FB133@codeaurora.org>

On Thursday 23 January 2014, Matthew Locke wrote:
> The QUP IP block is the same across chips.  Its possible there could be different versions of the IP block but its pretty stable now. 

Do you know the version numbers of the IP block? That would be the ideal case. We just
fall back to using the SoC name in most cases because that's all that is publically
known.

	Arnd

  reply	other threads:[~2014-01-23 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1389999819-10648-1-git-send-email-bjorn.andersson@sonymobile.com>
     [not found] ` <1389999819-10648-2-git-send-email-bjorn.andersson@sonymobile.com>
2014-01-20 14:10   ` [PATCH v3 1/2] i2c: qup: Add device tree bindings information Rob Herring
2014-01-21  2:40     ` Stephen Boyd
2014-01-24  7:18       ` Andy Gross
2014-01-23 19:11     ` Matthew Locke
2014-01-23 19:50       ` Arnd Bergmann [this message]
2014-01-23 20:22       ` Bjorn Andersson
     [not found] ` <1389999819-10648-3-git-send-email-bjorn.andersson@sonymobile.com>
2014-01-21  2:22   ` [PATCH v3 2/2] i2c: New bus driver for the QUP I2C controller Stephen Boyd
2014-01-24  1:25   ` Philip Elcan
2014-01-29  8:14 ` [PATCH v3 0/2] Qualcomm Universal Peripheral (QUP) " Ivan T. Ivanov
2014-01-29 16:32   ` Bjorn Andersson
2014-01-30 15:30     ` Ivan T. Ivanov
2014-01-30 23:27       ` Bjorn Andersson
2014-02-21  0:38 Bjorn Andersson
2014-02-21  0:38 ` [PATCH v3 1/2] i2c: qup: Add device tree bindings information Bjorn Andersson
2014-02-21 11:01   ` Mark Rutland

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=201401232050.25134.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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