public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Michal Simek <michal.simek@amd.com>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	u-boot@lists.denx.de, etienne.carriere@linaro.org,
	trini@konsulko.com, sjg@chromium.org, sughosh.ganu@linaro.org,
	xypron.glpk@gmx.de, takahiro.akashi@linaro.org,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>
Subject: Re: [PATCH v4 1/6] FWU: Add FWU metadata access driver for MTD storage regions
Date: Fri, 19 May 2023 15:21:15 +0300	[thread overview]
Message-ID: <ZGdpu6eIRSjv7x1L@hades> (raw)
In-Reply-To: <CABb+yY3KN9u8aaD_9ke=e2MFH9PGUWDnwTy1jutQ1h-Qqw4pzg@mail.gmail.com>

HI Jassi, Michal

Based on the discussion we had on the dt bindings, I am personally ok with
the notion of having those defined internally until we can prove it makes
sense for the to be sent to the dt-schema.

In the future we need to strip those from U-Boot, before we hand over the
DR to the OS, but this is a problem that already exists regardless of this patchset.

Jassi, Michal had some review comments.  Are you going to send a v5 with
those fixed?

Thanks
/Ilias

On Fri, Apr 14, 2023 at 10:09:11AM -0500, Jassi Brar wrote:
> On Fri, Apr 14, 2023 at 8:56 AM Michal Simek <michal.simek@amd.com> wrote:
> > On 4/10/23 05:56, Jassi Brar wrote:
> > > On Wed, 29 Mar 2023 at 07:00, Michal Simek <michal.simek@amd.com> wrote:
> > >> On 3/27/23 23:15, jassisinghbrar@gmail.com wrote:
> > >
> > >>> diff --git a/drivers/fwu-mdata/raw_mtd.c b/drivers/fwu-mdata/raw_mtd.c
> > >>> new file mode 100644
> > >>> index 0000000000..4b1a10073a
> > >>> --- /dev/null
> > >>> +++ b/drivers/fwu-mdata/raw_mtd.c
> > >>> @@ -0,0 +1,272 @@
> > >>> +// SPDX-License-Identifier: GPL-2.0+
> > >>
> > >> Just a note: Did you choose GPL-2.0+ by purpose? Or it is just c&p?
> > >>
> > > just c&p. though isn't that the same as GPL-2.0-or-later ?
> >
> > license choice is up to you. We normally use just gpl-2.0.
> >
> I think more than "we", the subsystem dictates licensing. All FWU code
> is under GPL-2.0-or-later.
> 
> 
> > >>
> > >> As I said this DT binding should be approved first to make sure that we don't
> > >> need to fix DT binding in future. Just simply do it right from the begining.
> > >>
> > > Yes, I will cc Rob in the next submission (I only forgot last time).
> > > However, let us note that fwu-mdata-gpt.yaml isn't blessed either.
> > > I am not sure if there is any reason for the fwu node to even be in
> > > the dts for kernel. But sure it is good to have it eyeballed by the DT
> > > gods.
> >
> > It doesn't really go to kernel.
> > Simon pushed options node directly to dt-schema
> > https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/options/u-boot.yaml#L96
> > And that would be also location for this node too.
> >
> Yes, but I have resend the already existisng bindings in uboot. My
> patch only modified them. Not a big problem.
> 
> -j

  reply	other threads:[~2023-05-19 12:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 21:14 [PATCH v4 0/6] FWU: Add support for mtd backed feature on DeveloperBox jassisinghbrar
2023-03-27 21:15 ` [PATCH v4 1/6] FWU: Add FWU metadata access driver for MTD storage regions jassisinghbrar
2023-03-29 11:59   ` Michal Simek
2023-04-10  3:56     ` Jassi Brar
2023-04-14 13:56       ` Michal Simek
2023-04-14 15:09         ` Jassi Brar
2023-05-19 12:21           ` Ilias Apalodimas [this message]
2023-05-19 12:45             ` Michal Simek
2023-05-19 20:54               ` Tom Rini
2023-03-27 21:16 ` [PATCH v4 2/6] FWU: mtd: Add helper functions for accessing FWU metadata jassisinghbrar
2023-03-29 11:55   ` Michal Simek
2023-04-10  4:02     ` Jassi Brar
2023-03-27 21:16 ` [PATCH v4 3/6] tools: Add mkfwumdata tool for FWU metadata image jassisinghbrar
2023-03-29 12:28   ` Michal Simek
2023-04-10  4:05     ` Jassi Brar
2023-04-14 13:53       ` Michal Simek
2023-04-14 15:02         ` Jassi Brar
2023-04-17  6:37           ` Michal Simek
2023-04-17 13:48             ` Jassi Brar
2023-04-17 14:29               ` Michal Simek
2023-04-17 14:50                 ` Jassi Brar
2023-03-29 20:02   ` Simon Glass
2023-04-10  4:25     ` Jassi Brar
2023-04-14 13:52       ` Michal Simek
2023-04-19  1:46         ` Simon Glass
2023-04-19  2:57           ` Jassi Brar
2023-04-19 22:40             ` Simon Glass
2023-03-30  6:07   ` Heinrich Schuchardt
2023-04-10  4:11     ` Jassi Brar
2023-03-27 21:16 ` [PATCH v4 4/6] dt: fwu: developerbox: enable fwu banks and mdata regions jassisinghbrar
2023-03-29 11:52   ` Michal Simek
2023-03-27 21:16 ` [PATCH v4 5/6] configs: move to new flash layout and boot flow jassisinghbrar
2023-03-27 21:16 ` [PATCH v4 6/6] fwu: DeveloperBox: add support for FWU jassisinghbrar
2023-03-29 13:01   ` Michal Simek
2023-04-10  4:21     ` Jassi Brar
2023-04-14 13:52       ` Michal Simek
2023-03-29 13:14 ` [PATCH v4 0/6] FWU: Add support for mtd backed feature on DeveloperBox Michal Simek
2023-03-30 13:35 ` 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=ZGdpu6eIRSjv7x1L@hades \
    --to=ilias.apalodimas@linaro.org \
    --cc=etienne.carriere@linaro.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=masami.hiramatsu@linaro.org \
    --cc=michal.simek@amd.com \
    --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