Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Akhila YS <akhilayalmati@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: microchip,mchp23k256: convert to DT schema
Date: Fri, 2 Jan 2026 15:38:50 +0530	[thread overview]
Message-ID: <cfe2550d-52d4-400e-903e-f32031ebd5ee@gmail.com> (raw)
In-Reply-To: <0363ac61-0872-42da-91b8-78966a2537ce@gmail.com>


On 02-01-2026 13:47, Akhila YS wrote:
>
>
> On 30-12-2025 18:02, Krzysztof Kozlowski wrote:
>> On Mon, Dec 29, 2025 at 12:49:00PM +0000, Akhila YS wrote:
>>> +---
>>> +$id: http://devicetree.org/schemas/mtd/microchip,mchp23k256.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Microchip 23K256 (and similar) SPI SRAM MTD driver
>> driver? Bindings are for hardware.
>
>
> Sure, I will fix it.
>
>>> +
>>> +maintainers:
>>> +  - Richard Weinberger <richard@nod.at>
>>> +
>>> +description: |
>> Do not need '|' unless you need to preserve formatting.
> Ok.
>>> +  Driver for Microchip 23K256 and compatible (e.g. 23LCV1024) serial SRAM devices
>> Don't describe drivers...
>>
>>> +  accessed via SPI. The device exposes the SRAM as an MTD device and supports
>>> +  optional partitioning via child nodes.
>> nor DTS, but the hardware.
>
>
> OK, I will change it.
>
>>> +
>>> +allOf:
>>> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
>>> +
>> If this is SRAM, then it should go to sram directory. But maybe it is
>> MTD, so NOR or NAND? If so you would be missing here refs to NAND
>> chips.
>>
>> Although docs are saying it is SRAM, so just place it there.
>
> This SRAM is not generic MMIO SRAM, it's an SPI peripheral exposing
> memory via the MTD subsystem. Also i tried Yaml from sram directory it
> doesn't work with it.
>
>>> +properties:
>>> +  compatible:
>>> +    enum:
>>> +      - microchip,mchp23k256
>>> +      - microchip,mchp23lcv1024
>>> +
>>> +  reg:
>>> +    maxItems: 1
>>> +
>>> +  "#address-cells":
>>> +    const: 1
>>> +
>>> +  "#size-cells":
>>> +    const: 1
>> Pretty incomplete. Old binding and above cells claim there can be child
>> nodes, so please add them and test. Works? No. Shall work? Yes... so
>> either old binding was incorrect or new binding is incomplete. I did not
>> check the driver, though.
>
>
> Size cells and Address cells are not required as there is no child
> node and I tried to define child node , Included SRAM.Yaml as a
> reference file and tested it. It doesn't work.
>
>>> +
>>> +required:
>>> +  - reg
>>> +  - compatible
>>> +  - "#address-cells"
>>> +  - "#size-cells"
>>> +  - spi-max-frequency
>>> +
>>> +unevaluatedProperties: false
>>> +
>>> +examples:
>>> +  - |
>>> +    spi {
>>> +        #address-cells = <1>;
>>> +        #size-cells = <0>;
>>> +
>>> +        sram@0 {
>>> +            #address-cells = <1>;
>>> +            #size-cells = <1>;
>> They are redundant. Where are children?
>
>
> They are redundant, There is no child node  and i will remove it.
>
>>> +            compatible = "microchip,mchp23k256";
>>> +            reg = <0>;
>>> +            spi-max-frequency = <20000000>;
>>> +        };
>>> +    };
>>> +...
>>>
>>> ---
>>> base-commit: cc3aa43b44bdb43dfbac0fcb51c56594a11338a8
>>> change-id: 20251229-nxp-526e29da9f29
>>>
>>> Best regards,
>>> -- 
>>> Akhila YS <akhilayalmati@gmail.com>
>>>
-- 
Best Regards,
Akhila.


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2026-01-02 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 12:49 [PATCH] dt-bindings: mtd: microchip,mchp23k256: convert to DT schema Akhila YS
2025-12-30 12:32 ` Krzysztof Kozlowski
     [not found]   ` <0363ac61-0872-42da-91b8-78966a2537ce@gmail.com>
2026-01-02 10:08     ` Akhila YS [this message]
2026-01-02 10:19       ` Krzysztof Kozlowski
2026-01-02 10:18     ` Krzysztof Kozlowski
2026-01-02 10:31       ` Akhila YS

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=cfe2550d-52d4-400e-903e-f32031ebd5ee@gmail.com \
    --to=akhilayalmati@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=vigneshr@ti.com \
    /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