[PATCH] 1wire: family module autoload fails because of upper/lower case mismatch.

2018-05-01 Thread Ingo Flaschberger
1wire family module autoload fails because of upper/lower  case mismatch. Signed-off-by: Ingo Flaschberger <ingo.flaschber...@gmail.com> ---  drivers/w1/w1.c | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c index ab0931e..aa458f2

[PATCH] 1wire: family module autoload fails because of upper/lower case mismatch.

2018-05-01 Thread Ingo Flaschberger
1wire family module autoload fails because of upper/lower  case mismatch. Signed-off-by: Ingo Flaschberger ---  drivers/w1/w1.c | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c index ab0931e..aa458f2 100644 --- a/drivers/w1/w1.c +++ b

[PATCH] 1wire: family module autoload fails because of upper/lower, case mismatch.

2018-04-11 Thread Ingo Flaschberger
1wire family module autoload fails because of upper/lower  case mismatch. Signed-off-by: Ingo Flaschberger <ingo.flaschber...@gmail.com> ---  drivers/w1/w1.c | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c index ab0931e..aa458f2

[PATCH] 1wire: family module autoload fails because of upper/lower, case mismatch.

2018-04-11 Thread Ingo Flaschberger
1wire family module autoload fails because of upper/lower  case mismatch. Signed-off-by: Ingo Flaschberger ---  drivers/w1/w1.c | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c index ab0931e..aa458f2 100644 --- a/drivers/w1/w1.c +++ b

w1_therm should not unlock bus if strong pullup is forced

2017-06-05 Thread Ingo Flaschberger
Hi, If strong pullup is forced (=2) a strong pullup is placed for 750ms. Is also external power detected the bus will be unlocked and a additional 750ms sleep is performed. This 2nd sleep should be avoided. Kind regards, Ingo Flaschberger --- w1_therm.c_org 2017-06-06 04:05

w1_therm should not unlock bus if strong pullup is forced

2017-06-05 Thread Ingo Flaschberger
Hi, If strong pullup is forced (=2) a strong pullup is placed for 750ms. Is also external power detected the bus will be unlocked and a additional 750ms sleep is performed. This 2nd sleep should be avoided. Kind regards, Ingo Flaschberger --- w1_therm.c_org 2017-06-06 04:05

Re: [PATCH] w1: gpio: Fix problematic platform_data usage

2016-03-22 Thread Ingo Flaschberger
Dear Markus, sorry - missed your reply last year. The patch seems to work. Kind regards, Ingo Flaschberger On Fri, Apr 10, 2015 at 12:22 PM, Markus Pargmann <m...@pengutronix.de> wrote: > Hi, > > On Mon, Mar 09, 2015 at 11:18:58AM +0100, Markus Pargmann wrote: >> pd

Re: [PATCH] w1: gpio: Fix problematic platform_data usage

2016-03-22 Thread Ingo Flaschberger
Dear Markus, sorry - missed your reply last year. The patch seems to work. Kind regards, Ingo Flaschberger On Fri, Apr 10, 2015 at 12:22 PM, Markus Pargmann wrote: > Hi, > > On Mon, Mar 09, 2015 at 11:18:58AM +0100, Markus Pargmann wrote: >> pdev->dev.platform_data should

Re: Fwd: Re: unbind/bind w1-gpio with device tree produce a crash

2015-03-05 Thread Ingo Flaschberger
structure too. Kind regards, Ingo Flaschberger -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: Fwd: Re: unbind/bind w1-gpio with device tree produce a crash

2015-03-05 Thread Ingo Flaschberger
. Kind regards, Ingo Flaschberger -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: unbind/bind w1-gpio with device tree produce a crash

2015-03-04 Thread Ingo Flaschberger
is it ok, to create a new global variable that tracks if pdata was alloced via devm_kzalloc and sets pdata to NULL in w1_gpio_remove? Am 04.03.2015 um 04:53 schrieb Ingo Flaschberger: If w1-gpio is probed via device-tree configuration, pdata is allocated via devm_kzalloc. When the device

Re: unbind/bind w1-gpio with device tree produce a crash

2015-03-04 Thread Ingo Flaschberger
is it ok, to create a new global variable that tracks if pdata was alloced via devm_kzalloc and sets pdata to NULL in w1_gpio_remove? Am 04.03.2015 um 04:53 schrieb Ingo Flaschberger: If w1-gpio is probed via device-tree configuration, pdata is allocated via devm_kzalloc. When the device

unbind/bind w1-gpio with device tree produce a crash

2015-03-03 Thread Ingo Flaschberger
If w1-gpio is probed via device-tree configuration, pdata is allocated via devm_kzalloc. When the device is unbind (and bind later) the allocated memory of pdate is freed - but it will not be allocacted again. static int w1_gpio_probe(struct platform_device *pdev) struct w1_bus_master

unbind/bind w1-gpio with device tree produce a crash

2015-03-03 Thread Ingo Flaschberger
If w1-gpio is probed via device-tree configuration, pdata is allocated via devm_kzalloc. When the device is unbind (and bind later) the allocated memory of pdate is freed - but it will not be allocacted again. static int w1_gpio_probe(struct platform_device *pdev) struct w1_bus_master