devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Nelson <robertcnelson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: John Carter <john.carter-U313QQUz4dygSpxsJD1C4w@public.gmane.org>
Cc: devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Status of drivers/of/configfs.c
Date: Tue, 29 Aug 2017 20:13:40 -0500	[thread overview]
Message-ID: <CAOCHtYiifaWwRQJ8frZRtz=V6WeRnxE1AYLXwpZ9FJ7Am1vB-A@mail.gmail.com> (raw)
In-Reply-To: <CAFD1m3FQ6vNF9sUU67g_VE5nKsHWk-MfmHiVqyjpZmoq544AxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi John,

On Tue, Aug 29, 2017 at 5:37 PM, John Carter <john.carter-U313QQUz4dygSpxsJD1C4w@public.gmane.org> wrote:
> In 2014 Pantelis Antoniou sent a patch...
>     https://lkml.org/lkml/2014/3/18/625
> ...creating an interface between the config filesystem and devicetree overlays.
>
> As far as I can see it is used in a couple of "off the mainstream
> kernel" like the beaglebone black.
>
> Alas, at this stage it doesn't seem to have made it into the upstream
> kernel.....
>
> 1) What is the status of this patch? Is it still being maintained? If so where?
>
> 2) My interest in it is for an nasty bit of oddball hardware.
>
> I have to change a pin from being an gpio input at boot time to being
> a uart output sometime after boot.
>
> Would the of / configfs be the best way of doing that or is there a better way?

I think most of us have given up on making it work in the kernel, just
too many race conditions.

I'd say for the last half year we (beagleboard) have been focusing on
moving to u-boot overlays.  Just less issues when you have the
device-tree-binary setup in a proper state at kernel boot.

Regards,

-- 
Robert Nelson
https://rcn-ee.com/
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2017-08-30  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 22:37 Status of drivers/of/configfs.c John Carter
     [not found] ` <CAFD1m3FQ6vNF9sUU67g_VE5nKsHWk-MfmHiVqyjpZmoq544AxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-30  1:13   ` Robert Nelson [this message]

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='CAOCHtYiifaWwRQJ8frZRtz=V6WeRnxE1AYLXwpZ9FJ7Am1vB-A@mail.gmail.com' \
    --to=robertcnelson-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=john.carter-U313QQUz4dygSpxsJD1C4w@public.gmane.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).