devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brazdil <dbrazdil@google.com>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Will Deacon <will@kernel.org>,
	Andrew Scull <ascull@google.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: firmware: Add Open Profile for DICE
Date: Wed, 15 Dec 2021 21:08:29 +0000	[thread overview]
Message-ID: <YbpZTSpmnieCNZ9a@google.com> (raw)
In-Reply-To: <YbpPYG4rzPmJmwA6@robh.at.kernel.org>

Hi Rob,

> > +        dice_reserved: dice@12340000 {
> > +            reg = <0x00 0x12340000 0x2000>;
> > +            no-map;
> > +        };
> > +    };
> > +
> > +    dice {
> > +        compatible = "google,open-dice";
> > +        memory-region = <&dice_reserved>;
> 
> There's no need for this indirection. Just add the compatible to the 
> dice@12340000 node. You can bind drivers to /reserved-memory nodes.

I have not found a way to make that work for kernel modules. Built-in
drivers can bind with RESERVEDMEM_OF_DECLARE, which puts an entry in
__reservedmem_of_table and __reserved_mem_init_node() iterates find it
there. A good case study might be CONFIG_TEGRA210_EMC, where the driver
itself can be a module but the rmem parsing is always built-in under
CONFIG_TEGRA210_EMC_TABLE. I don't think that's worth the trouble with
this driver.

David

  reply	other threads:[~2021-12-15 21:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 19:58 [PATCH v3 0/2] Driver for Open Profile for DICE David Brazdil
2021-12-13 19:58 ` [PATCH v3 1/2] dt-bindings: firmware: Add " David Brazdil
2021-12-15 20:26   ` Rob Herring
2021-12-15 21:08     ` David Brazdil [this message]
2021-12-16 15:21       ` Rob Herring
2021-12-21 17:43         ` David Brazdil
2021-12-13 19:58 ` [PATCH v3 2/2] misc: open-dice: Add driver to expose DICE data to userspace David Brazdil
2021-12-14  3:25   ` kernel test robot
2021-12-14  3:56   ` kernel test robot
2021-12-14  7:18   ` Greg Kroah-Hartman
2021-12-14 14:37     ` David Brazdil

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=YbpZTSpmnieCNZ9a@google.com \
    --to=dbrazdil@google.com \
    --cc=arnd@arndb.de \
    --cc=ascull@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=will@kernel.org \
    /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).