Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1481541

Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers

From Warner Losh <imp@bsdimp.com>
Newsgroups linux.kernel
Subject Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers
Date 2016-09-12 18:50 +0200
Message-ID <sgCAF-5NW-19@gated-at.bofh.it> (permalink)
References (3 earlier) <sgyGK-3jx-29@gated-at.bofh.it> <sgzjr-3N9-5@gated-at.bofh.it> <sgA5Q-4ka-21@gated-at.bofh.it> <sgApc-4s1-21@gated-at.bofh.it> <sgChk-5GQ-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, Sep 12, 2016 at 10:29 AM, Sebastian Frias <sf84@laposte.net> wrote:
> Hi Warner,
>
> On 09/12/2016 04:26 PM, Warner Losh wrote:
>> On Mon, Sep 12, 2016 at 8:01 AM, Mark Rutland <mark.rutland@arm.com> wrote:
>>>> Since the question seems understood, do you have an example of other SoC's
>>>> doing something similar?
>>>
>>> I do not have an example. I know that others are using DT for data
>>> beyond what Linux or another OS requires, but it's my understanding that
>>> that is typically in a separate DTB.
>>
>> Just to clarify: FreeBSD uses, for the most part, the DTB's that the
>> 'vendor' ships, which is quite often the same ones included in Linux.
>> There's some exceptions where the bindings weren't really hardware
>> independent, or where the abstraction model was really Linux specific
>> (for things like the HDMI stack).
>>
>> However, with the advent of overlays, one would think that a vendor
>> could easily include an overlay with the DTB data for the devices they
>> don't wish to, or cannot for other reasons release. It seems like the
>> perfect mechanism to comply with the rules about inclusion of nodes in
>> the DTS. Vendors are free to document these nodes and don't require
>> the Linux kernel include them in the Documents directory to do so.
>> There have been recent efforts to move this documentation to a third
>> party to maintain.
>
> This is very interesting, do you have a more concrete example of such
> usage?

Using overlays to layer in a proprietary device blob for a proprietary driver?
No. I don't. It just seems like a natural solution. Do I have more examples
where FreeBSD has to deviate because the DT is actually Linux
specific and does a poor job of modeling the hardware and instead
reflects the Linux driver model? I have plenty of those...

Warner

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: ARM,SoC: About the use DT-defined properties by 3rd-party drivers Sebastian Frias <sf84@laposte.net> - 2016-09-12 14:30 +0200
  Re: ARM,SoC: About the use DT-defined properties by 3rd-party drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-12 14:40 +0200
    Re: ARM,SoC: About the use DT-defined properties by 3rd-party drivers Sebastian Frias <sf84@laposte.net> - 2016-09-12 15:20 +0200
      Re: ARM,SoC: About the use DT-defined properties by 3rd-party drivers Timur Tabi <timur@tabi.org> - 2016-09-12 15:30 +0200
      Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-12 16:10 +0200
        Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers Warner Losh <imp@bsdimp.com> - 2016-09-12 16:30 +0200
          Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-12 18:30 +0200
            Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers Warner Losh <imp@bsdimp.com> - 2016-09-12 18:50 +0200
              Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Timur Tabi <timur@tabi.org> - 2016-09-12 18:50 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-12 19:10 +0200
              Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-12 19:50 +0200
        Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-12 18:10 +0200
          Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-12 18:30 +0200
          Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Timur Tabi <timur@tabi.org> - 2016-09-12 18:30 +0200
          Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-12 19:00 +0200
            Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-13 12:10 +0200
              Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Timur Tabi <timur@tabi.org> - 2016-09-13 13:40 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-13 15:30 +0200
              Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-13 15:20 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-13 16:30 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-13 17:00 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-14 10:40 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-13 17:00 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Mark Rutland <mark.rutland@arm.com> - 2016-09-13 17:50 +0200
                Re: ARM, SoC: About the use DT-defined properties by 3rd-party  drivers Sebastian Frias <sf84@laposte.net> - 2016-09-14 10:30 +0200

csiph-web