Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Arnd Bergmann
On Monday 11 February 2013 16:48:12 Samuel Ortiz wrote: > > > If so, how do you know which transport to use? > Through the mei_bus_client ops. Device drivers get a mei_bus_client pointer > from their probe routine and the ops pointers there (If any) are set by > whoever creates the device. In the

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Samuel Ortiz
Hi Arnd, On Mon, Feb 11, 2013 at 03:08:24PM +, Arnd Bergmann wrote: > On Monday 11 February 2013, Samuel Ortiz wrote: > > On Mon, Feb 11, 2013 at 11:52:42AM +, Arnd Bergmann wrote: > > > On Thursday 07 February 2013, Samuel Ortiz wrote: > > > > On Thu, Feb 07, 2013 at 10:34:44PM +,

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Arnd Bergmann
On Monday 11 February 2013, Samuel Ortiz wrote: > On Mon, Feb 11, 2013 at 11:52:42AM +, Arnd Bergmann wrote: > > On Thursday 07 February 2013, Samuel Ortiz wrote: > > > On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: > > > > On Thursday 07 February 2013, Tomas Winkler wrote: > >

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Samuel Ortiz
Hi Arnd, On Mon, Feb 11, 2013 at 11:52:42AM +, Arnd Bergmann wrote: > On Thursday 07 February 2013, Samuel Ortiz wrote: > > On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: > > > On Thursday 07 February 2013, Tomas Winkler wrote: > > > > + > > > > +struct mei_bus_ops { > > > > +

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Arnd Bergmann
On Thursday 07 February 2013, Samuel Ortiz wrote: > On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: > > On Thursday 07 February 2013, Tomas Winkler wrote: > > > + > > > +struct mei_bus_ops { > > > + int (*send)(struct mei_bus_client *client, u8 *buf, size_t > > > length); > >

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Arnd Bergmann
On Thursday 07 February 2013, Samuel Ortiz wrote: On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Tomas Winkler wrote: + +struct mei_bus_ops { + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length); + int

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Samuel Ortiz
Hi Arnd, On Mon, Feb 11, 2013 at 11:52:42AM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Samuel Ortiz wrote: On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Tomas Winkler wrote: + +struct mei_bus_ops { + int

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Arnd Bergmann
On Monday 11 February 2013, Samuel Ortiz wrote: On Mon, Feb 11, 2013 at 11:52:42AM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Samuel Ortiz wrote: On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Tomas Winkler wrote: +

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Samuel Ortiz
Hi Arnd, On Mon, Feb 11, 2013 at 03:08:24PM +, Arnd Bergmann wrote: On Monday 11 February 2013, Samuel Ortiz wrote: On Mon, Feb 11, 2013 at 11:52:42AM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Samuel Ortiz wrote: On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-11 Thread Arnd Bergmann
On Monday 11 February 2013 16:48:12 Samuel Ortiz wrote: If so, how do you know which transport to use? Through the mei_bus_client ops. Device drivers get a mei_bus_client pointer from their probe routine and the ops pointers there (If any) are set by whoever creates the device. In the NFC

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-07 Thread Samuel Ortiz
Hi Arnd, On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: > On Thursday 07 February 2013, Tomas Winkler wrote: > > + > > +struct mei_bus_ops { > > + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length); > > + int (*recv)(struct mei_bus_client *client, u8

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-07 Thread Arnd Bergmann
On Thursday 07 February 2013, Tomas Winkler wrote: > + > +struct mei_bus_ops { > + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length); > + int (*recv)(struct mei_bus_client *client, u8 *buf, size_t length); > +}; > + Can you have more than one set of mei_bus_ops in a

[char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-07 Thread Tomas Winkler
From: Samuel Ortiz Signed-off-by: Samuel Ortiz Signed-off-by: Tomas Winkler --- drivers/misc/mei/bus.c | 226 drivers/misc/mei/bus.h |3 + drivers/misc/mei/mei_dev.h | 14 +++ include/linux/mei_bus.h| 11 ++ 4 files changed,

[char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-07 Thread Tomas Winkler
From: Samuel Ortiz sa...@linux.intel.com Signed-off-by: Samuel Ortiz sa...@linux.intel.com Signed-off-by: Tomas Winkler tomas.wink...@intel.com --- drivers/misc/mei/bus.c | 226 drivers/misc/mei/bus.h |3 + drivers/misc/mei/mei_dev.h |

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-07 Thread Arnd Bergmann
On Thursday 07 February 2013, Tomas Winkler wrote: + +struct mei_bus_ops { + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length); + int (*recv)(struct mei_bus_client *client, u8 *buf, size_t length); +}; + Can you have more than one set of mei_bus_ops in a driver?

Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

2013-02-07 Thread Samuel Ortiz
Hi Arnd, On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote: On Thursday 07 February 2013, Tomas Winkler wrote: + +struct mei_bus_ops { + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length); + int (*recv)(struct mei_bus_client *client, u8 *buf,