From: Mark Brown <broonie@kernel.org>
To: matthew.gerlach@linux.intel.com
Cc: hao.wu@intel.com, trix@redhat.com, mdf@kernel.org,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
yilun.xu@intel.com, jdelvare@suse.com, linux@roeck-us.net,
lee.jones@linaro.org, linux-hwmon@vger.kernel.org,
russell.h.weight@intel.com, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 1/2] spi: Add DFL bus driver for Altera SPI Master
Date: Thu, 15 Apr 2021 12:44:24 +0100 [thread overview]
Message-ID: <20210415114424.GA5514@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104141203480.482712@rhweight-WRK1>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
On Wed, Apr 14, 2021 at 12:09:50PM -0700, matthew.gerlach@linux.intel.com wrote:
> On Wed, 14 Apr 2021, Mark Brown wrote:
> > Don't create a platform device here, extend the spi-altera driver to
> > register with both DFL and platform buses.
> Are you suggesting something like the SPI driver for the Designware
> controller where there is spi-dw-core.c and bus specific code like
> spi-dw-pci.c and spi-dw-mmioc.c?
Yes, exactly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-15 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 22:58 [PATCH v2 0/2] spi: add BMC support for Intel D5005 card matthew.gerlach
2021-04-13 22:58 ` [PATCH v2 1/2] spi: Add DFL bus driver for Altera SPI Master matthew.gerlach
2021-04-14 14:18 ` Mark Brown
2021-04-14 19:09 ` matthew.gerlach
2021-04-15 11:44 ` Mark Brown [this message]
2021-04-14 15:29 ` Tom Rix
2021-04-13 22:58 ` [PATCH v2 2/2] hwmon: intel-m10-bmc-hwmon: add sensor support of Intel D5005 card matthew.gerlach
2021-04-13 23:11 ` Guenter Roeck
2021-04-14 15:36 ` Tom Rix
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=20210415114424.GA5514@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hao.wu@intel.com \
--cc=jdelvare@suse.com \
--cc=lee.jones@linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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;
as well as URLs for NNTP newsgroup(s).