mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Jan Glauber <jglauber@cavium.com>,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	David Daney <david.daney@cavium.com>,
	"Steven J . Hill" <steven.hill@cavium.com>
Subject: Re: [PATCH v2 2/2] spi: octeon: Add thunderx driver
Date: Tue, 2 Aug 2016 22:30:18 +0100	[thread overview]
Message-ID: <20160802213018.GL10376@sirena.org.uk> (raw)
In-Reply-To: <579F9CDE.5050207@caviumnetworks.com>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

On Mon, Aug 01, 2016 at 12:02:54PM -0700, David Daney wrote:
> On 08/01/2016 11:49 AM, Mark Brown wrote:

> > What is that thing on ACPI systems?

> I don't know if it works ACPI, or if ACPI even has support for the clock
> framework.  But does it matter?  We are not currently using ACPI on systems
> where this driver is used.

> In the future, if we ever need ACPI support, we will add support for it.

Oh, that's surprising - I thought these were server systems.  With ACPI
you need to use DMI data or something to instantiate the clock.  In any
case if you've got it working that should be OK.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-08-02 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  8:31 [PATCH v2 0/2] SPI ThunderX driver Jan Glauber
2016-07-28  8:31 ` [PATCH v2 1/2] spi: octeon: Split driver into Octeon specific and common parts Jan Glauber
2016-08-01 17:36   ` Mark Brown
2016-07-28  8:31 ` [PATCH v2 2/2] spi: octeon: Add thunderx driver Jan Glauber
2016-08-01 17:28   ` Mark Brown
2016-08-01 18:31     ` David Daney
2016-08-01 18:49       ` Mark Brown
2016-08-01 19:02         ` David Daney
2016-08-02 21:30           ` Mark Brown [this message]
2016-08-02 21:49             ` David Daney

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=20160802213018.GL10376@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=david.daney@cavium.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=jglauber@cavium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=steven.hill@cavium.com \
    /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

all inboxes | Powered by JetHome®