On Mon, Feb 11, 2013 at 04:58:54PM +0100, Samuel Ortiz wrote:
> On Mon, Feb 11, 2013 at 06:30:51AM -0800, Greg KH wrote:
> > On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
> > > > You already have a 'struct mei_device', which refers to the PCI device
> > > > that owns the bus, and
On Mon, Feb 11, 2013 at 06:30:51AM -0800, Greg KH wrote:
> On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
> > > You already have a 'struct mei_device', which refers to the PCI device
> > > that owns the bus, and has clients attached to it. While it may be
> > > a little confusing to
On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
> > You already have a 'struct mei_device', which refers to the PCI device
> > that owns the bus, and has clients attached to it. While it may be
> > a little confusing to people that already worked with the current
> > mei code, I
Hi Arnd,
On Mon, Feb 11, 2013 at 11:50:26AM +, Arnd Bergmann wrote:
> On Sunday 10 February 2013, Samuel Ortiz wrote:
> > > >
> > > > /**
> > > > + * mei_bus_client
> > >
> > > I don't really understand this structure, please explain it better.
> > This is a structure that links the MEI
On Sunday 10 February 2013, Samuel Ortiz wrote:
> > >
> > > /**
> > > + * mei_bus_client
> >
> > I don't really understand this structure, please explain it better.
> This is a structure that links the MEI bus client pointer passed to the driver
> with the actual ME client. It also allows the
On Sunday 10 February 2013, Samuel Ortiz wrote:
/**
+ * mei_bus_client
I don't really understand this structure, please explain it better.
This is a structure that links the MEI bus client pointer passed to the driver
with the actual ME client. It also allows the ME driver to
Hi Arnd,
On Mon, Feb 11, 2013 at 11:50:26AM +, Arnd Bergmann wrote:
On Sunday 10 February 2013, Samuel Ortiz wrote:
/**
+ * mei_bus_client
I don't really understand this structure, please explain it better.
This is a structure that links the MEI bus client pointer
On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
You already have a 'struct mei_device', which refers to the PCI device
that owns the bus, and has clients attached to it. While it may be
a little confusing to people that already worked with the current
mei code, I think it
On Mon, Feb 11, 2013 at 06:30:51AM -0800, Greg KH wrote:
On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
You already have a 'struct mei_device', which refers to the PCI device
that owns the bus, and has clients attached to it. While it may be
a little confusing to people
On Mon, Feb 11, 2013 at 04:58:54PM +0100, Samuel Ortiz wrote:
On Mon, Feb 11, 2013 at 06:30:51AM -0800, Greg KH wrote:
On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
You already have a 'struct mei_device', which refers to the PCI device
that owns the bus, and has clients
Hi Greg,
On Fri, Feb 08, 2013 at 03:53:41PM -0800, Greg KH wrote:
> > +Example
> > +===
> > +As a theoretical example let's pretend the ME comes with a "contact" NFC
> > IP.
> > +The driver init and exit routines for this device would look like:
> > +
> > +#define CONTACT_DRIVER_NAME
Hi Greg,
On Fri, Feb 08, 2013 at 03:53:41PM -0800, Greg KH wrote:
+Example
+===
+As a theoretical example let's pretend the ME comes with a contact NFC
IP.
+The driver init and exit routines for this device would look like:
+
+#define CONTACT_DRIVER_NAME contact
+
+#define
On Fri, Feb 08, 2013 at 02:28:14PM +0200, Tomas Winkler wrote:
> From: Samuel Ortiz
>
> mei bus will present some of the me clients
> as devices for other standard subsystems
>
> Implement the probe, remove, match and the device addtion routines.
> A mei-bus.txt document describing the
From: Samuel Ortiz
mei bus will present some of the me clients
as devices for other standard subsystems
Implement the probe, remove, match and the device addtion routines.
A mei-bus.txt document describing the rationale and the API usage
is also added.
Signed-off-by: Samuel Ortiz
From: Samuel Ortiz sa...@linux.intel.com
mei bus will present some of the me clients
as devices for other standard subsystems
Implement the probe, remove, match and the device addtion routines.
A mei-bus.txt document describing the rationale and the API usage
is also added.
Signed-off-by:
On Fri, Feb 08, 2013 at 02:28:14PM +0200, Tomas Winkler wrote:
From: Samuel Ortiz sa...@linux.intel.com
mei bus will present some of the me clients
as devices for other standard subsystems
Implement the probe, remove, match and the device addtion routines.
A mei-bus.txt document
16 matches
Mail list logo
