On Thu, 3 Jan 2008 15:48:35 +0200
Ville Syrjälä <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 26, 2007 at 11:24:54PM +0100, Haavard Skinnemoen wrote:
> > On Fri, 21 Dec 2007 09:34:01 +0200
> > Ville Syrjala <[EMAIL PROTECTED]> wrote:
> >
> > > +static struct platform_device foo_w1_device = {
> > > +
On Wed, Dec 26, 2007 at 11:24:54PM +0100, Haavard Skinnemoen wrote:
> On Fri, 21 Dec 2007 09:34:01 +0200
> Ville Syrjala <[EMAIL PROTECTED]> wrote:
>
> > +static struct platform_device foo_w1_device = {
> > + .name = "w1-gpio",
> > + .id = -1,
>
>
On Wed, Dec 26, 2007 at 11:24:54PM +0100, Haavard Skinnemoen wrote:
On Fri, 21 Dec 2007 09:34:01 +0200
Ville Syrjala [EMAIL PROTECTED] wrote:
+static struct platform_device foo_w1_device = {
+ .name = w1-gpio,
+ .id = -1,
Assigning -1 to a u32
On Thu, 3 Jan 2008 15:48:35 +0200
Ville Syrjälä [EMAIL PROTECTED] wrote:
On Wed, Dec 26, 2007 at 11:24:54PM +0100, Haavard Skinnemoen wrote:
On Fri, 21 Dec 2007 09:34:01 +0200
Ville Syrjala [EMAIL PROTECTED] wrote:
+static struct platform_device foo_w1_device = {
+ .name
On Fri, 21 Dec 2007 09:34:01 +0200
Ville Syrjala <[EMAIL PROTECTED]> wrote:
> +static struct platform_device foo_w1_device = {
> + .name = "w1-gpio",
> + .id = -1,
Assigning -1 to a u32 member isn't a very nice example. What does it
mean anyway?
>
On Fri, 21 Dec 2007 09:34:01 +0200
Ville Syrjala [EMAIL PROTECTED] wrote:
+static struct platform_device foo_w1_device = {
+ .name = w1-gpio,
+ .id = -1,
Assigning -1 to a u32 member isn't a very nice example. What does it
mean anyway?
+static
On Fri, Dec 21, 2007 at 02:45:46PM +0200, Ville Syrjala ([EMAIL PROTECTED])
wrote:
> Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
> control the wire and the GPIO pin can be specified using platform data
> similar to i2c-gpio. The driver was tested with AT91SAM9260 +
On Fri, Dec 21, 2007 at 01:41:28PM +0300, Evgeniy Polyakov wrote:
> Hi Ville.
>
> On Fri, Dec 21, 2007 at 09:34:01AM +0200, Ville Syrjala ([EMAIL PROTECTED])
> wrote:
> > Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
> > control the wire and the GPIO pin can be specified
Hi Ville.
On Fri, Dec 21, 2007 at 09:34:01AM +0200, Ville Syrjala ([EMAIL PROTECTED])
wrote:
> Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
> control the wire and the GPIO pin can be specified using platform data
> similar to i2c-gpio. The driver was tested with
Hi Ville.
On Fri, Dec 21, 2007 at 09:34:01AM +0200, Ville Syrjala ([EMAIL PROTECTED])
wrote:
Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
control the wire and the GPIO pin can be specified using platform data
similar to i2c-gpio. The driver was tested with AT91SAM9260
On Fri, Dec 21, 2007 at 02:45:46PM +0200, Ville Syrjala ([EMAIL PROTECTED])
wrote:
Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
control the wire and the GPIO pin can be specified using platform data
similar to i2c-gpio. The driver was tested with AT91SAM9260 + DS2401.
On Fri, Dec 21, 2007 at 01:41:28PM +0300, Evgeniy Polyakov wrote:
Hi Ville.
On Fri, Dec 21, 2007 at 09:34:01AM +0200, Ville Syrjala ([EMAIL PROTECTED])
wrote:
Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
control the wire and the GPIO pin can be specified using
12 matches
Mail list logo