public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Sughosh Ganu <sughosh.ganu@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	jaswinder.singh@linaro.org, u-boot@lists.denx.de,
	krzysztof.kozlowski+dt@linaro.org, etienne.carriere@linaro.org,
	trini@konsulko.com, sjg@chromium.org, xypron.glpk@gmx.de,
	takahiro.akashi@linaro.org, michal.simek@amd.com
Subject: Re: [PATCH] dt/bindings: fwu-mdata-mtd: drop changes outside FWU
Date: Thu, 4 May 2023 15:08:53 +0300	[thread overview]
Message-ID: <ZFOgVYJRY2giHC8/@hera> (raw)
In-Reply-To: <CADg8p94qCSoAALSNA2vMCfGVXSYPKgnP1u=Nqf7nCDJAAiqoUg@mail.gmail.com>


[...]

> > > I'm assuming it's per partition type rather than storage medium (e.g.
> > > SATA, USB, SD, NAND, SPI-NOR)? GPT, 'fixed-partitions', other DT
> > > partition bindings, etc. If so, then I'm really wondering why it's a
> > > standalone tree rather than integrated into those existing partition
> > > bindings.
> >
> > I think it's per medium, unless I misunderstood something.  Sughosh?
>
> The bindings would be required as per the metadata access mechanism.
> So for example, the MTD bindings would suffice for all the storage
> mediums which would have MTD based partitioning schemes. Same for all
> GPT partitioned devices. Again, as for the need for a separate node
> with the compatible property, it is as per the driver model design.
> For the other properties, we can indeed have them integrated with the
> corresponding partition bindings.

Ok, Rob is correct then it really is per partition type.

Thanks
/Ilias
>
> -sughosh

  reply	other threads:[~2023-05-04 12:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 23:21 [PATCH] dt/bindings: fwu-mdata-mtd: drop changes outside FWU jaswinder.singh
2023-04-11  5:38 ` Krzysztof Kozlowski
2023-04-14 14:01   ` Michal Simek
2023-05-03 14:37   ` Ilias Apalodimas
2023-05-03 14:54     ` Krzysztof Kozlowski
2023-05-03 16:26       ` Tom Rini
2023-05-03 16:32         ` Krzysztof Kozlowski
2023-05-03 17:24     ` Rob Herring
2023-05-04 10:45       ` Ilias Apalodimas
2023-05-04 11:57         ` Sughosh Ganu
2023-05-04 12:08           ` Ilias Apalodimas [this message]
2023-05-04 14:01             ` Jassi Brar
2023-05-04 15:19               ` Rob Herring
2023-05-04 15:39                 ` Jassi Brar
2023-05-04 16:19                   ` Tom Rini
2023-05-04 16:30                     ` Ilias Apalodimas
2023-05-04 16:41                       ` Jassi Brar
2023-05-05 15:47                         ` Rob Herring
2023-05-05  8:38                 ` Michal Simek

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=ZFOgVYJRY2giHC8/@hera \
    --to=ilias.apalodimas@linaro.org \
    --cc=etienne.carriere@linaro.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=michal.simek@amd.com \
    --cc=robh+dt@kernel.org \
    --cc=sjg@chromium.org \
    --cc=sughosh.ganu@linaro.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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