On 10/20/25 12:44 PM, Conor Dooley wrote:
> On Mon, Oct 20, 2025 at 11:51:44AM -0500, Alex Elder wrote:
>> Allow two resets to be optionally included for the Freescale QSPI driver.
>
> This is a binding, please don't mention the driver here.
OK, I will reword it in v2.
>> Signed-off-by: Alex Elder <elder@riscstar.com>
>> ---
>> Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml b/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml
>> index f2dd20370dbb3..0315a13fe319a 100644
>> --- a/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml
>> +++ b/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml
>> @@ -54,6 +54,11 @@ properties:
>> - const: qspi_en
>> - const: qspi
>>
>> + resets:
>> + items:
>> + - description: SoC QSPI reset
>> + - description: SoC QSPI bus reset
>
> If none of the fsl devices have resets, this should be added alongside
> the new spacemit compatible and not permitted for the other compatibles.
I thought that, being optional, this kind of constraint wasn't
strictly necessary.
Anyway, I'll find out first whether the resets are even required,
and if they are I'll rework this the way you suggest.
Thank you for your very quick review.
-Alex
>> +
>> required:
>> - compatible
>> - reg
>> --
>> 2.48.1
>>