lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aTa6moPSbWk7+S6u@shlinux89>
Date: Mon, 8 Dec 2025 19:46:34 +0800
From: Peng Fan <peng.fan@....nxp.com>
To: Haixu Cui <quic_haixcui@...cinc.com>, Mark Brown <broonie@...nel.org>
Cc: virtualization@...ts.linux.dev, linux-spi@...r.kernel.org,
	linux-kernel@...r.kernel.org, Peng Fan <peng.fan@....com>
Subject: Re: [PATCH RFC] spi: virtio: Add [new,delete]_device sysfs interface

On Fri, Dec 05, 2025 at 09:40:26PM +0800, Peng Fan (OSS) wrote:
>From: Peng Fan <peng.fan@....com>
>
>spi-virtio registers a SPI controller, but we still need to register a
>SPI device to initiate the SPI virtio transfer.
>
>To Xen hypervisor, there might be no 'passthrough' node for DomU,
>so add a sysfs interface to allow creating/deleting a SPI device.
>
>Usage:
> echo "spidev" > /sys/class/spi_master/spi0/new_device
> echo "spi0.0" > /sys/class/spi_master/spi0/delete_device
>

After rethinking about this, I think it might be better to add the sysfs
to all SPI controller just as what i2c core supports:
drivers/i2c/i2c-core-base.c: 1264

I will post out v2 to move the code to spi_controller_groups if no objections.

Thanks,
Peng

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ