Hello Krzysztof,
On 02/17/2016 04:49 AM, Krzysztof Kozlowski wrote:
On 17.02.2016 05:45, Javier Martinez Canillas wrote:
[snip]
By "please check" in this case I mean - look if every regulator/clock
consumer using stuff exposed by PMIC, supports properly deferred probing.
Got it, I
Hello Krzysztof,
On 02/17/2016 04:49 AM, Krzysztof Kozlowski wrote:
On 17.02.2016 05:45, Javier Martinez Canillas wrote:
[snip]
By "please check" in this case I mean - look if every regulator/clock
consumer using stuff exposed by PMIC, supports properly deferred probing.
Got it, I
On 17.02.2016 18:27, Marek Szyprowski wrote:
> Hello,
>
> On 2016-02-16 00:20, Krzysztof Kozlowski wrote:
>> On 16.02.2016 00:21, Javier Martinez Canillas wrote:
>>> Hello Krzysztof,
>>>
>>> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas
On 17.02.2016 18:27, Marek Szyprowski wrote:
> Hello,
>
> On 2016-02-16 00:20, Krzysztof Kozlowski wrote:
>> On 16.02.2016 00:21, Javier Martinez Canillas wrote:
>>> Hello Krzysztof,
>>>
>>> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas
Hello,
On 2016-02-16 00:20, Krzysztof Kozlowski wrote:
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do anything besides
Hello,
On 2016-02-16 00:20, Krzysztof Kozlowski wrote:
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do anything besides
On 17.02.2016 05:45, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/15/2016 08:20 PM, Krzysztof Kozlowski wrote:
>> On 16.02.2016 00:21, Javier Martinez Canillas wrote:
>>> Hello Krzysztof,
>>>
>>> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier
On 17.02.2016 05:45, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/15/2016 08:20 PM, Krzysztof Kozlowski wrote:
>> On 16.02.2016 00:21, Javier Martinez Canillas wrote:
>>> Hello Krzysztof,
>>>
>>> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier
Hello Krzysztof,
On 02/15/2016 08:20 PM, Krzysztof Kozlowski wrote:
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do
Hello Krzysztof,
On 02/15/2016 08:20 PM, Krzysztof Kozlowski wrote:
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
>> On 12.02.2016 13:30, Javier Martinez Canillas wrote:
>>> The driver's init and exit function don't do anything besides adding and
>>> deleting the I2C driver so the
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
>> On 12.02.2016 13:30, Javier Martinez Canillas wrote:
>>> The driver's init and exit function don't do anything besides adding and
>>> deleting the I2C driver so the
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do anything besides adding and
deleting the I2C driver so the module_i2c_driver() macro could be used.
Currently is not being used
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do anything besides adding and
deleting the I2C driver so the module_i2c_driver() macro could be used.
Currently is not being used
On Mon, 15 Feb 2016, Krzysztof Kozlowski wrote:
> On 12.02.2016 13:30, Javier Martinez Canillas wrote:
> > The driver's init and exit function don't do anything besides adding and
> > deleting the I2C driver so the module_i2c_driver() macro could be used.
> >
> > Currently is not being used
On Mon, 15 Feb 2016, Krzysztof Kozlowski wrote:
> On 12.02.2016 13:30, Javier Martinez Canillas wrote:
> > The driver's init and exit function don't do anything besides adding and
> > deleting the I2C driver so the module_i2c_driver() macro could be used.
> >
> > Currently is not being used
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
> The driver's init and exit function don't do anything besides adding and
> deleting the I2C driver so the module_i2c_driver() macro could be used.
>
> Currently is not being used because the driver is initialized at subsys
> initcall level,
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
> The driver's init and exit function don't do anything besides adding and
> deleting the I2C driver so the module_i2c_driver() macro could be used.
>
> Currently is not being used because the driver is initialized at subsys
> initcall level,
The driver's init and exit function don't do anything besides adding and
deleting the I2C driver so the module_i2c_driver() macro could be used.
Currently is not being used because the driver is initialized at subsys
initcall level, claiming that this is done to allow consumers devices to
use the
The driver's init and exit function don't do anything besides adding and
deleting the I2C driver so the module_i2c_driver() macro could be used.
Currently is not being used because the driver is initialized at subsys
initcall level, claiming that this is done to allow consumers devices to
use the
20 matches
Mail list logo
