public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: matthew.gerlach@linux.intel.com
Cc: vndao@altera.com, dwmw2@infradead.org,
	computersforpeace@gmail.com, boris.brezillon@free-electrons.com,
	richard@nod.at, cyrille.pitchen@wedev4u.fr, robh+dt@kernel.org,
	mark.rutland@arm.com, linux-mtd@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, davem@davemloft.net,
	mchehab@kernel.org
Subject: Re: [PATCH 3/3] mtd: spi-nor: Altera Quadspi Flash Controller v2 Platform driver
Date: Tue, 27 Jun 2017 18:21:43 +0200	[thread overview]
Message-ID: <5f0e2ddd-d329-cb3d-01bc-c101247281a7@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1706270800240.8058@mgerlach-VirtualBox>

On 06/27/2017 05:15 PM, matthew.gerlach@linux.intel.com wrote:
> 
> 
> On Tue, 27 Jun 2017, Marek Vasut wrote:
> 
>> On 06/26/2017 06:13 PM, matthew.gerlach@linux.intel.com wrote:
>>> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>>
>> Just wrap it into the Altera QSPI driver , no need for separate platform
>> driver IMO.
> 
> Hi Marek,
> 
> I answered this question when you asked why the header file was
> necessary, but I think further discussion could be helpful, since this
> problem is becoming more prevelent.  The Altera Quadspi component is a
> soft IP in a
> FPGA, and the processor using the component may or may not have device
> tree support compiled into the Linux kernel.  Since device tree support
> may or may not be available, the device tree specific code must be
> separated
> from the core driver code.

I see, that's fine, although there is no PCIe or other support in this
submission. Is that planned ?

> One can certainly make the case, that device tree support could/should
> be available everywhere, but the current reality is most x86 Linux
> kernel configurations do not include device tree support.
> 
> For the record, I believe device trees, and more specifically device
> tree overlays, are the best way for Linux to use FPGAs, but I have to
> deal with the current realities.
> 
> Thanks again for all the great feedback.
> 
> Matthew Gerlach

[...]

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2017-06-27 16:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 16:13 [PATCH 0/3] Altera Quadspi Controller Version 2 matthew.gerlach
2017-06-26 16:13 ` [PATCH 1/3] ARM: dts: Bindings for " matthew.gerlach
2017-06-27  9:37   ` Marek Vasut
2017-06-27 14:32     ` matthew.gerlach
2017-06-27 15:01       ` Marek Vasut
2017-06-27 15:57         ` matthew.gerlach
2017-06-27 16:15           ` Marek Vasut
2017-06-27 17:18             ` matthew.gerlach
2017-06-27 17:52               ` Marek Vasut
2017-06-27 19:32                 ` matthew.gerlach
2017-06-27 19:56                   ` Marek Vasut
2017-06-28 23:09           ` Rob Herring
2017-06-29  9:43             ` Marek Vasut
2017-06-29 15:03               ` matthew.gerlach
2017-06-29 15:38                 ` Marek Vasut
2017-06-28 23:14   ` Rob Herring
2017-06-26 16:13 ` [PATCH 2/3] mtd: spi-nor: core code for the Altera Quadspi Flash Controller v2 matthew.gerlach
2017-06-27  9:30   ` kbuild test robot
2017-06-27  9:48   ` Marek Vasut
2017-06-27 14:57     ` matthew.gerlach
2017-06-27 16:19       ` Marek Vasut
2017-06-27 17:26         ` matthew.gerlach
2017-06-27 17:55           ` Marek Vasut
2017-06-27 19:44             ` matthew.gerlach
2017-07-04  0:00   ` Cyrille Pitchen
2017-07-04 10:38     ` Michal Suchanek
2017-07-05 14:34     ` matthew.gerlach
2017-06-26 16:13 ` [PATCH 3/3] mtd: spi-nor: Altera Quadspi Flash Controller v2 Platform driver matthew.gerlach
2017-06-27  9:49   ` Marek Vasut
2017-06-27 15:15     ` matthew.gerlach
2017-06-27 16:21       ` Marek Vasut [this message]
2017-06-27 17:38         ` matthew.gerlach
2017-06-27 10:55   ` kbuild test robot

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=5f0e2ddd-d329-cb3d-01bc-c101247281a7@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=mchehab@kernel.org \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=vndao@altera.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