linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 4/9] mfd: Add binding document for NVIDIA Tegra XUSB
Date: Thu, 21 May 2015 09:19:00 +0200	[thread overview]
Message-ID: <CACRpkdbK4BBhs==yFWW91M_4x5f3RGDiXBV+yBYYQ78JG0mMLg@mail.gmail.com> (raw)
In-Reply-To: <20150520145227.GA3787@ulmo.nvidia.com>

On Wed, May 20, 2015 at 4:52 PM, Thierry Reding
<thierry.reding@gmail.com> wrote:

> I'm a little confused by the simple-mfd approach. The only code I see in
> linux-next for this is a single line that adds the "simple-mfd" string
> to the OF device ID table in drivers/of/platform.c. As far as I can tell
> this will merely cause child devices to be created. There won't be a
> shared regmap and resources won't be set up properly either.

That is correct. The simple-mfd is a two-component approach.

Ideally, in the simplest case, you combine simple-mfd with syscon.

foo at 0 {
    compatible = "foo", "syscon", "simple-mfd";
    reg = <0x10000000 0x1000>;

    bar at 1 {
        compatible = "bar";
    };

    baz at 2 {
        compatible = "baz";
    };
};

This will instantiate bar and baz.

These subdrivers then probe and:

probe() {
   struct regmap *map;

   map = syscon_node_to_regmap(parent->of_node);
   (...)
}

Simple, syscon is the MFD hub.

Yours,
Linus Walleij

  reply	other threads:[~2015-05-21  7:19 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 17:36 [PATCH v8 0/9] Tegra xHCI support Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 1/9] xhci: Set shared HCD's hcd_priv in xhci_gen_setup Andrew Bresticker
2015-05-19 18:39   ` Andrew Bresticker
2015-05-22 12:19     ` Mathias Nyman
2015-05-04 17:36 ` [PATCH v8 2/9] mailbox: Make mbox_chan_ops const Andrew Bresticker
2015-05-04 19:22   ` Suman Anna
2015-05-04 17:36 ` [PATCH v8 3/9] mailbox: Fix up error handling in mbox_request_channel() Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 4/9] mfd: Add binding document for NVIDIA Tegra XUSB Andrew Bresticker
2015-05-13 14:39   ` Lee Jones
2015-05-13 16:26     ` Andrew Bresticker
2015-05-13 16:50       ` Lee Jones
2015-05-13 17:03         ` Andrew Bresticker
2015-05-14  7:29           ` Lee Jones
2015-05-14  7:32             ` Jon Hunter
2015-05-14  7:45               ` Lee Jones
2015-05-14  7:20     ` Jon Hunter
2015-05-14  7:40       ` Lee Jones
2015-05-14  9:14         ` Jon Hunter
2015-05-14  9:30           ` Lee Jones
2015-05-14 10:09             ` Jon Hunter
2015-05-14 10:23               ` Lee Jones
2015-05-14 11:21                 ` Jon Hunter
2015-05-14 17:38         ` Andrew Bresticker
2015-05-19 18:36           ` Andrew Bresticker
2015-05-20  6:35             ` Lee Jones
2015-05-20 14:52               ` Thierry Reding
2015-05-21  7:19                 ` Linus Walleij [this message]
2015-05-21  8:40                 ` Lee Jones
2015-05-21 10:12                   ` Thierry Reding
2015-05-26 15:18                     ` Lee Jones
2015-06-30 18:22                       ` Grant Likely
2015-05-04 17:36 ` [PATCH v8 5/9] mfd: Add driver " Andrew Bresticker
2015-05-13 14:37   ` Lee Jones
2015-05-13 16:31     ` Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 6/9] mailbox: Add NVIDIA Tegra XUSB mailbox binding Andrew Bresticker
2015-05-08 20:42   ` Benson Leung
2015-05-08 20:53     ` Andrew Bresticker
2015-05-08 21:03       ` Benson Leung
2015-05-04 17:36 ` [PATCH v8 7/9] mailbox: Add NVIDIA Tegra XUSB mailbox driver Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 8/9] usb: Add NVIDIA Tegra xHCI controller binding Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 9/9] usb: xhci: Add NVIDIA Tegra xHCI host-controller driver Andrew Bresticker
2015-05-05 14:28 ` [PATCH v8 0/9] Tegra xHCI support Jon Hunter
2015-05-05 14:42   ` Thierry Reding
2015-05-05 14:57     ` Jon Hunter
2015-05-12  3:56 ` Jassi Brar
2015-05-26 16:27   ` Andrew Bresticker

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='CACRpkdbK4BBhs==yFWW91M_4x5f3RGDiXBV+yBYYQ78JG0mMLg@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).