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 08/10] spi: espi_amd: Add support for IO/MMIO configuration
Date: Wed, 26 Mar 2025 15:42:06 +0530	[thread overview]
Message-ID: <836f2d63-7b9a-4fef-ba52-3d481ea91077@amd.com> (raw)
In-Reply-To: <b409f5e3-2259-4427-8d4a-1652e7fec135@sirena.org.uk>



On 3/17/2025 7:40 PM, Mark Brown wrote:
> On Fri, Mar 14, 2025 at 12:04:38AM +0530, Raju Rangoju wrote:
> 
>> Add support to configure the eSPI slave0 IO/MMIO address before
>> initiating the peripheral channel IO/MMIO read and write operations.
>> This patch introduces new IOCTLs to enable, disable and read IO/MMIO
>> configurations.
> 
> This absolutely does not seem like something that should be exposed to
> userspace, if there is some reason for this to be runtime configured it
> needs to be clearly explained.

Hi Mark,

Thanks for reviewing this. In subsequent series we are planning to drop 
the IOCTLS that are exposed to userspace

  reply	other threads:[~2025-03-26 10:12 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 [this message]
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

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=836f2d63-7b9a-4fef-ba52-3d481ea91077@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