public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rangoju, Raju" <raju.rangoju@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	krishnamoorthi.m@amd.com, akshata.mukundshetty@amd.com
Subject: Re: [PATCH 00/10] spi: Add driver to support AMD eSPI controller
Date: Wed, 2 Apr 2025 17:13:17 +0530	[thread overview]
Message-ID: <c239f4ce-98d3-4896-989c-3f1e4e5ad0d1@amd.com> (raw)
In-Reply-To: <6a67247e-0b20-42fc-ac0b-7d4a8cef410c@sirena.org.uk>



On 3/26/2025 4:35 PM, Mark Brown wrote:
> On Wed, Mar 26, 2025 at 03:25:21PM +0530, Rangoju, Raju wrote:
>> On 3/17/2025 7:44 PM, Mark Brown wrote:
> 
>>> I see nothing in this series that registers a SPI controller with the
>>> SPI core.  You need to use the standard frameworks the kernel offers to
>>> provide standard functionality.
> 
>> The AMD SPI controller hardware has only the chip select line enabled, which
>> is connected to the EC slave in AMD EMB platforms. Currently, there is no
>> support from the slave device to register as an SPI slave device with the
>> SPI framework and provide SPI communication.
> 
>> For this reason, the AMD eSPI driver is designed to handle device
>> initialization itself and provide a character device file as an interface
>> with user space for dynamic interaction and configurations.
> 
> If you want to ignore the SPI subsystem and just write a driver for your
> embedded controller then you should put the driver in the subsystem or
> subsystems for that embedded controller (possibly MFD if it does a bunch
> of things), not SPI.  Even if there is no flexibility you may still want
> to have the controller side in the SPI subsystem in order to help with
> reuse with different controller/EC combinations but if you're going that
> way you need to use the SPI subsystem.

Thanks for the suggestions Mark. We will rework on this.

      reply	other threads:[~2025-04-02 11:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 18:34 [PATCH 00/10] spi: Add driver to support AMD eSPI controller Raju Rangoju
2025-03-13 18:34 ` [PATCH 01/10] spi: espi_amd: Add AMD eSPI controller driver support Raju Rangoju
2025-03-17 14:06   ` Mark Brown
2025-03-26 10:00     ` Rangoju, Raju
2025-03-13 18:34 ` [PATCH 02/10] spi: espi_amd: Add eSPI set config IOCTL command Raju Rangoju
2025-03-17 14:07   ` Mark Brown
2025-03-26 10:03     ` Rangoju, Raju
2025-03-13 18:34 ` [PATCH 03/10] spi: espi_amd: Add eSPI get " Raju Rangoju
2025-03-13 18:34 ` [PATCH 04/10] spi: espi_amd: Add eSPI inband-reset " Raju Rangoju
2025-03-13 18:34 ` [PATCH 05/10] spi: espi_amd: Add eSPI set IO mode " Raju Rangoju
2025-03-13 18:34 ` [PATCH 06/10] spi: espi_amd: Add eSPI set channel " Raju Rangoju
2025-03-13 18:34 ` [PATCH 07/10] spi: espi_amd: Add eSPI set frequency " Raju Rangoju
2025-03-13 18:34 ` [PATCH 08/10] spi: espi_amd: Add support for IO/MMIO configuration Raju Rangoju
2025-03-17 14:10   ` Mark Brown
2025-03-26 10:12     ` Rangoju, Raju
2025-03-13 18:34 ` [PATCH 09/10] spi: espi_amd: Add eSPI PC channel IO read/write IOCTL commands Raju Rangoju
2025-03-13 18:34 ` [PATCH 10/10] spi: espi_amd: Add eSPI PC channel MMIO " Raju Rangoju
2025-03-17 14:14 ` [PATCH 00/10] spi: Add driver to support AMD eSPI controller Mark Brown
2025-03-26  9:55   ` Rangoju, Raju
2025-03-26 11:05     ` Mark Brown
2025-04-02 11:43       ` Rangoju, Raju [this message]

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=c239f4ce-98d3-4896-989c-3f1e4e5ad0d1@amd.com \
    --to=raju.rangoju@amd.com \
    --cc=akshata.mukundshetty@amd.com \
    --cc=broonie@kernel.org \
    --cc=krishnamoorthi.m@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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