linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
	robh+dt@kernel.org
Cc: bjorn.andersson@linaro.org, linux-mtd@lists.infradead.org,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Add support for Qcom SMEM based NAND parser
Date: Thu, 10 Dec 2020 09:39:42 +0530	[thread overview]
Message-ID: <20201210040942.GD6466@thinkpad> (raw)
In-Reply-To: <20201119071308.9292-1-manivannan.sadhasivam@linaro.org>

Hi,

On Thu, Nov 19, 2020 at 12:43:04PM +0530, Manivannan Sadhasivam wrote:
> Hello,
> 
> This series adds support for parsing the partitions defined in Shared
> Memory (SMEM) of the Qualcomm platforms supporting NAND interface.
> Current parser only supports V3 and V4 of the partition tables.
> 
> This series has been tested on SDX55 MTP board which has an onboard NAND
> device.
> 

Any update on this series?

Thanks,
Mani

> Thanks,
> Mani
> 
> Changes in v3:
> 
> * Handled le32 parameters in parser, collected review from Linus W.
> 
> Changes in v2:
> 
> * Added additionalProperties: false and removed unit address in binding
> 
> Manivannan Sadhasivam (4):
>   dt-bindings: mtd: partitions: Add binding for Qcom SMEM parser
>   mtd: parsers: Add Qcom SMEM parser
>   mtd: rawnand: qcom: Add support for Qcom SMEM parser
>   mtd: parsers: afs: Fix freeing the part name memory in failure
> 
>  .../mtd/partitions/qcom,smem-part.yaml        |  33 ++++
>  drivers/mtd/nand/raw/qcom_nandc.c             |   4 +-
>  drivers/mtd/parsers/Kconfig                   |   8 +
>  drivers/mtd/parsers/Makefile                  |   1 +
>  drivers/mtd/parsers/afs.c                     |   4 +-
>  drivers/mtd/parsers/qcomsmempart.c            | 170 ++++++++++++++++++
>  6 files changed, 216 insertions(+), 4 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/mtd/partitions/qcom,smem-part.yaml
>  create mode 100644 drivers/mtd/parsers/qcomsmempart.c
> 
> -- 
> 2.17.1
> 

  parent reply	other threads:[~2020-12-10  4:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  7:13 [PATCH v3 0/4] Add support for Qcom SMEM based NAND parser Manivannan Sadhasivam
2020-11-19  7:13 ` [PATCH v3 1/4] dt-bindings: mtd: partitions: Add binding for Qcom SMEM parser Manivannan Sadhasivam
2020-12-07 21:52   ` Rob Herring
2020-12-11  3:31     ` Manivannan Sadhasivam
2020-12-11 21:13       ` Rob Herring
2020-11-19  7:13 ` [PATCH v3 2/4] mtd: parsers: Add " Manivannan Sadhasivam
2020-11-19  7:13 ` [PATCH v3 3/4] mtd: rawnand: qcom: Add support for " Manivannan Sadhasivam
2020-11-19  7:13 ` [PATCH v3 4/4] mtd: parsers: afs: Fix freeing the part name memory in failure Manivannan Sadhasivam
2020-12-10  4:09 ` Manivannan Sadhasivam [this message]
2020-12-10 21:24   ` [PATCH v3 0/4] Add support for Qcom SMEM based NAND parser Miquel Raynal
2020-12-11  3:10     ` Rob Herring
2020-12-11  3:36       ` Manivannan Sadhasivam

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=20201210040942.GD6466@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.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+dt@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;
as well as URLs for NNTP newsgroup(s).