From: gregkh@linuxfoundation•org (Greg KH)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH] Documentation: devicetree: add description for generic bus properties
Date: Fri, 29 Nov 2013 10:11:23 -0800 [thread overview]
Message-ID: <20131129181123.GA7113@kroah.com> (raw)
In-Reply-To: <20131129180110.GJ31000@mudshark.cambridge.arm.com>
On Fri, Nov 29, 2013 at 06:01:10PM +0000, Will Deacon wrote:
> On Fri, Nov 29, 2013 at 05:37:01PM +0000, Greg KH wrote:
> > On Fri, Nov 29, 2013 at 11:44:53AM +0000, Will Deacon wrote:
> > > On Thu, Nov 28, 2013 at 09:25:28PM +0000, Greg KH wrote:
> > > > On Thu, Nov 28, 2013 at 07:39:17PM +0000, Dave Martin wrote:
> > > > > On Thu, Nov 28, 2013 at 11:13:31AM -0800, Greg KH wrote:
> > > > > > Yes it is, you all are the ones tasked with implementing the crazy crap
> > > > > > the hardware people have created, best of luck with that :)
> > > > >
> > > > > Agreed. The first assumption should be that we can fit in with the
> > > > > existing device model -- we should only reconsider if we find that
> > > > > to be impossible.
> > > >
> > > > Let me know if you think it is somehow impossible, but you all should
> > > > really push back on the insane hardware designers that are forcing you
> > > > all to do this work. I find it "interesting" how this all becomes your
> > > > workload for their crazy ideas.
> > >
> > > Oh, I don't think we're claiming anything is impossible here :) It's more
> > > that we will probably want to make some changes to the device model to allow,
> > > for example, a device to be associated with multiple buses of potentially
> > > different types.
> >
> > Why would you want that? What good would that help with?
>
> It would help with devices which have their slave interface on one bus, but
> master to another.
>
> We need a way to configure the master side of things (IOMMU, coherency, MSI
> routing, etc) on one bus and configure the slave side (device probing, power
> management, clocks, etc) on another.
Make this two "devices" and have each "device" have a pointer or a way
to "find" the other one.
next prev parent reply other threads:[~2013-11-29 18:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 17:28 [RFC PATCH] Documentation: devicetree: add description for generic bus properties Dave Martin
2013-11-27 23:06 ` Greg KH
2013-11-28 10:28 ` Will Deacon
2013-11-28 17:33 ` Dave Martin
2013-11-28 19:13 ` Greg KH
2013-11-28 19:39 ` Dave Martin
2013-11-28 21:25 ` Greg KH
2013-11-29 11:44 ` Will Deacon
2013-11-29 17:37 ` Greg KH
2013-11-29 18:01 ` Will Deacon
2013-11-29 18:11 ` Greg KH [this message]
2013-11-29 18:15 ` Will Deacon
2013-11-28 19:10 ` Greg KH
2013-11-28 20:33 ` Thierry Reding
2013-11-28 21:10 ` Jason Gunthorpe
2013-11-28 22:22 ` Thierry Reding
2013-11-28 23:31 ` Jason Gunthorpe
2013-11-29 2:35 ` Greg KH
2013-11-29 9:37 ` Thierry Reding
2013-11-29 9:57 ` Russell King - ARM Linux
2013-11-29 10:43 ` Thierry Reding
2013-11-29 13:13 ` Dave Martin
2013-11-29 13:29 ` Russell King - ARM Linux
2013-11-29 17:43 ` Greg KH
2013-11-29 17:42 ` Greg KH
2013-11-29 19:45 ` Thierry Reding
2013-12-04 18:43 ` Mark Brown
2013-12-04 19:03 ` Greg KH
2013-12-04 20:27 ` Mark Brown
2013-11-29 9:57 ` Thierry Reding
2013-11-29 14:13 ` Dave Martin
2013-11-29 11:58 ` Dave Martin
2013-11-29 18:43 ` Jason Gunthorpe
2013-12-02 20:25 ` Dave Martin
2013-12-03 0:07 ` Jason Gunthorpe
2013-12-03 11:45 ` Dave Martin
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=20131129181123.GA7113@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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