[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f0477df-7228-4cb0-ad08-52a35f2976e1@amd.com>
Date: Wed, 26 Mar 2025 15:33:58 +0530
From: "Rangoju, Raju" <raju.rangoju@....com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
krishnamoorthi.m@....com, akshata.mukundshetty@....com
Subject: Re: [PATCH 02/10] spi: espi_amd: Add eSPI set config IOCTL command
On 3/17/2025 7:37 PM, Mark Brown wrote:
> On Fri, Mar 14, 2025 at 12:04:32AM +0530, Raju Rangoju wrote:
>
>> This patch introduces an IOCTL command to set the configuration of the
>> eSPI controller and eSPI slave0. The configuration options include
>> parameters like frequency, channel, and IO mode. The new IOCTL command
>> allow users to dynamically configure the eSPI controller and slave.
>
> Why? We have spidev...
There is no support from the slave device side to register as an SPI
slave device with the SPI framework and provide SPI communication.
For this reason, the AMD eSPI driver can only handle device
initialization itself and provide a character device file as an
interface to user space.
Powered by blists - more mailing lists