lkml.org 
[lkml]   [2022]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v3 4/4] mtd: core: Fix a conflict between MTD and NVMEM on wp-gpios property
    Hi Srinivas,

    christophe.kerello@foss.st.com wrote on Thu, 17 Feb 2022 15:47:55 +0100:

    > Wp-gpios property can be used on NVMEM nodes and the same property can
    > be also used on MTD NAND nodes. In case of the wp-gpios property is
    > defined at NAND level node, the GPIO management is done at NAND driver
    > level. Write protect is disabled when the driver is probed or resumed
    > and is enabled when the driver is released or suspended.
    >
    > When no partitions are defined in the NAND DT node, then the NAND DT node
    > will be passed to NVMEM framework. If wp-gpios property is defined in
    > this node, the GPIO resource is taken twice and the NAND controller
    > driver fails to probe.
    >
    > A new Boolean flag named ignore_wp has been added in nvmem_config.
    > In case ignore_wp is set, it means that the GPIO is handled by the
    > provider. Lets set this flag in MTD layer to avoid the conflict on
    > wp_gpios property.
    >
    > Fixes: 2a127da461a9 ("nvmem: add support for the write-protect pin")
    > Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
    > Cc: stable@vger.kernel.org

    You can take patches 3 and 4 through the nvmem tree.

    Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>

    Thanks,
    Miquèl

    \
     
     \ /
      Last update: 2022-02-18 14:22    [W:2.956 / U:0.060 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site