devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Grant Likely <grant.likely@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] of/platform: Allow secondary compatible match in of_dev_lookup
Date: Tue, 12 Apr 2016 08:13:27 -0700	[thread overview]
Message-ID: <20160412151326.GL5995@atomide.com> (raw)
In-Reply-To: <87d1q1r7o3.fsf@intel.com>

* Felipe Balbi <felipe.balbi@linux.intel.com> [160407 04:19]:
> Grygorii Strashko <grygorii.strashko@ti.com> writes:
> > Most probably this is required to pass some data from parent device to
> > children when parent dev instantiate children from DT, at least I've experimented with
> > this in mostly similar way (I've not added second pass and did break in the first
> > if !phys_addr, but Tony's patch is more correct).

OK that's a different use case I have, but good to know it helps
with that too.

> > For example,
> > - USB dwc3 platform/integration layer dev creates DWC3-core device (of_platform_populate())
> > - DWC3-core device creates xhci device
> > - USB dwc3 platform/integration layer dev can dynamically get rev info
> >   from HW and identify limitation/erratas/quirks which need to be applied to 
> >   to its children.
> > - DWC3-core can dynamically get rev info ...
> >
> > I was not able to find any other proper way to pass this (platfrom)data to children, except
> > using Auxdata. And, as per Felipe Balbi, It was the major reason why now
> > DWC3-core device creates xhci device manually.
> 
> doesn't device_property() solve that ? I'm just waiting for some patches
> from Heikki (in Cc) before we rip pdata from dwc3 completely. At that
> point, we can look at building xhci from DT.
> 
> The only thing that comes to mind is how this will look for PCI-only
> systems if we rip manual xHCI device creation completely.

Sounds like this dwc3 thread is a bit separate from the $subject patch
except for the legacy usage.

Regards,

Tony

  reply	other threads:[~2016-04-12 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 21:35 [PATCH] of/platform: Allow secondary compatible match in of_dev_lookup Tony Lindgren
     [not found] ` <1459546504-32668-1-git-send-email-tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-04-01 21:40   ` Tony Lindgren
     [not found]     ` <20160401214053.GQ9329-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-04-07  4:52       ` Rob Herring
     [not found]         ` <CAL_Jsq+PcTD=duHmWgHyx_ywYbT10vEtcm=79x5o5wYSkgG63g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-07 10:21           ` Grygorii Strashko
     [not found]             ` <5706348C.1040709-l0cyMroinI0@public.gmane.org>
2016-04-07 11:15               ` Felipe Balbi
2016-04-12 15:13                 ` Tony Lindgren [this message]
2016-04-07 16:58         ` Tony Lindgren
     [not found]           ` <20160407165842.GJ16484-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-04-12 15:56             ` Rob Herring
     [not found]               ` <CAL_Jsq+XrNoqEjCnQ=rLJVdQe9EdHb+MopUtvM2vy12N2veo3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-12 16:31                 ` Tony Lindgren

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=20160412151326.GL5995@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=felipe.balbi@linux.intel.com \
    --cc=frowand.list@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@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).