Re: mechanism to allow a driver to bind to any device

2014-03-31 Thread Alex Williamson
On Mon, 2014-03-31 at 17:36 -0500, Kim Phillips wrote: > On Fri, 28 Mar 2014 11:10:23 -0600 > Alex Williamson wrote: > > > On Fri, 2014-03-28 at 12:58 -0400, Konrad Rzeszutek Wilk wrote: > > > On Wed, Mar 26, 2014 at 04:09:21PM -0600, Alex Williamson wrote: > > > > On Wed, 2014-03-26 at 10:21 -06

Re: mechanism to allow a driver to bind to any device

2014-03-31 Thread Kim Phillips
On Fri, 28 Mar 2014 11:10:23 -0600 Alex Williamson wrote: > On Fri, 2014-03-28 at 12:58 -0400, Konrad Rzeszutek Wilk wrote: > > On Wed, Mar 26, 2014 at 04:09:21PM -0600, Alex Williamson wrote: > > > On Wed, 2014-03-26 at 10:21 -0600, Alex Williamson wrote: > > > > On Wed, 2014-03-26 at 23:06 +080

Re: mechanism to allow a driver to bind to any device

2014-03-31 Thread Kim Phillips
On Mon, 31 Mar 2014 20:23:36 + Stuart Yoder wrote: > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Monday, March 31, 2014 2:47 PM > > > > On Mon, Mar 31, 2014 at 06:47:51PM +, Stuart Yoder wrote: > > > I also, was at the point where I thought we should perhaps just > > >

RE: mechanism to allow a driver to bind to any device

2014-03-31 Thread Stuart Yoder
> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Monday, March 31, 2014 2:47 PM > To: Yoder Stuart-B08248 > Cc: Alex Williamson; Alexander Graf; k...@vger.kernel.org; > jan.kis...@siemens.com; will.dea...@arm.com; > a.r...@virtualopensystems.com; Michal Hoc

Re: mechanism to allow a driver to bind to any device

2014-03-31 Thread Greg KH
On Mon, Mar 31, 2014 at 06:47:51PM +, Stuart Yoder wrote: > I also, was at the point where I thought we should perhaps just > go with current mechanisms and implement new_id for the platform > bus...but Greg's recent response is 'platform devices suck' and it sounds > like he would reject a new

RE: mechanism to allow a driver to bind to any device

2014-03-31 Thread Stuart Yoder
> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, March 26, 2014 5:09 PM > To: Alexander Graf > Cc: k...@vger.kernel.org; jan.kis...@siemens.com; will.dea...@arm.com; > Yoder Stuart-B08248; a.r...@virtualopensystems.com; Michal Hocko; Wood

RE: mechanism to allow a driver to bind to any device

2014-03-31 Thread Stuart Yoder
> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, March 26, 2014 11:21 AM > To: Alexander Graf > Cc: Konrad Rzeszutek Wilk; k...@vger.kernel.org; jan.kis...@siemens.com; > will.dea...@arm.com; Yoder Stuart-B08248; linux-ker...@vger.kernel.

RE: mechanism to allow a driver to bind to any device

2014-03-31 Thread Stuart Yoder
> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Friday, March 28, 2014 2:00 AM > To: Antonios Motakis > Cc: Yoder Stuart-B08248; alex.william...@redhat.com; > kvm...@lists.cs.columbia.edu; iommu@lists.linux-foundation.org; linux- > ker...@vger.kernel.org;

Re: [PATCH 4/5] ARM: shmobile: r8a7791: Add IPMMU DT nodes

2014-03-31 Thread Ben Dooks
On 31/03/14 15:01, Laurent Pinchart wrote: Hi Geert, On Monday 31 March 2014 10:52:28 Geert Uytterhoeven wrote: On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: + ipmmu_sy0: mmu@e6280800 { + compatible = "renesas,ipmmu-vmsa"; + reg = <0 0xe6280800 0 0

Re: [PATCH 3/5] iommu/ipmmu-vmsa: Add device tree support

2014-03-31 Thread Laurent Pinchart
Hi Geert, On Monday 31 March 2014 10:45:00 Geert Uytterhoeven wrote: > On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: > > @@ -828,16 +829,31 @@ static phys_addr_t ipmmu_iova_to_phys(struct > > iommu_domain *io_domain,> > > static int ipmmu_find_utlb(struct ipmmu_vmsa_device *mmu, stru

Re: [PATCH 4/5] ARM: shmobile: r8a7791: Add IPMMU DT nodes

2014-03-31 Thread Laurent Pinchart
Hi Geert, On Monday 31 March 2014 10:52:28 Geert Uytterhoeven wrote: > On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: > > + ipmmu_sy0: mmu@e6280800 { > > + compatible = "renesas,ipmmu-vmsa"; > > + reg = <0 0xe6280800 0 0x800>; > > Shouldn't this be "re

Re: [PATCH 2/5] iommu/ipmmu-vmsa: Add device tree bindings documentation

2014-03-31 Thread Laurent Pinchart
Hi Geert, On Monday 31 March 2014 10:39:48 Geert Uytterhoeven wrote: > On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: > > +Required Properties: > > + > > + - compatible: Must contain "renesas,ipmmu-vmsa". > > + - reg: Base address and size of the IPMMU registers. > > + - interrupts:

Re: [PATCH 4/5] ARM: shmobile: r8a7791: Add IPMMU DT nodes

2014-03-31 Thread Geert Uytterhoeven
Hi Laurent, On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: > + ipmmu_sy0: mmu@e6280800 { > + compatible = "renesas,ipmmu-vmsa"; > + reg = <0 0xe6280800 0 0x800>; Shouldn't this be "reg = <0 0xe628 0 0x1000>", i.e. expose both banks? Is there any

Re: [PATCH 3/5] iommu/ipmmu-vmsa: Add device tree support

2014-03-31 Thread Geert Uytterhoeven
Hi Laurent, On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: > @@ -828,16 +829,31 @@ static phys_addr_t ipmmu_iova_to_phys(struct > iommu_domain *io_domain, > > static int ipmmu_find_utlb(struct ipmmu_vmsa_device *mmu, struct device *dev) > { > + ret = of_parse_phandle_with_fix

Re: [PATCH 2/5] iommu/ipmmu-vmsa: Add device tree bindings documentation

2014-03-31 Thread Geert Uytterhoeven
Hi Laurent, On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote: > +Required Properties: > + > + - compatible: Must contain "renesas,ipmmu-vmsa". > + - reg: Base address and size of the IPMMU registers. > + - interrupts: Specifier for the MMU fault interrupt. Does it make sense to have a