This patch fixes by detaching the event related information from
chip_info struct,
and based on channel type and event direction the corresponding
event configuration registers
are picked dynamically. Hence multiple events can be handled in
read/write callbacks.
which chip can have which
This patch fixes by detaching the event related information from
chip_info struct,
and based on channel type and event direction the corresponding
event configuration registers
are picked dynamically. Hence multiple events can be handled in
read/write callbacks.
which chip can have which
On Thu, 17 Aug 2017 07:55:45 -0400
Harinath Nampally wrote:
> > This patch fixes by detaching the event related information from
> > chip_info struct,
> >>> and based on channel type and event direction the corresponding
> > event configuration registers
> >>> are
On Thu, 17 Aug 2017 07:55:45 -0400
Harinath Nampally wrote:
> > This patch fixes by detaching the event related information from
> > chip_info struct,
> >>> and based on channel type and event direction the corresponding
> > event configuration registers
> >>> are picked dynamically. Hence
This patch fixes by detaching the event related information from
chip_info struct,
and based on channel type and event direction the corresponding
event configuration registers
are picked dynamically. Hence multiple events can be handled in
read/write callbacks.
which chip can have which
This patch fixes by detaching the event related information from
chip_info struct,
and based on channel type and event direction the corresponding
event configuration registers
are picked dynamically. Hence multiple events can be handled in
read/write callbacks.
which chip can have which
Am 17. August 2017 02:39:05 MESZ schrieb Harinath Nampally
:
>> Hello,
>>
>> fixes are always welcome, some comments regarding the patch
>Thanks for the review.
>>
>> in subject: typo "enable"
>Will fix it.
>>> This driver supports multiple devices like mma8653, mma8652,
Am 17. August 2017 02:39:05 MESZ schrieb Harinath Nampally
:
>> Hello,
>>
>> fixes are always welcome, some comments regarding the patch
>Thanks for the review.
>>
>> in subject: typo "enable"
>Will fix it.
>>> This driver supports multiple devices like mma8653, mma8652,
>mma8452, mma8453 and
Hello,
fixes are always welcome, some comments regarding the patch
Thanks for the review.
in subject: typo "enable"
Will fix it.
This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
and
fxls8471. Almost all these devices have more than one event. Current driver
Hello,
fixes are always welcome, some comments regarding the patch
Thanks for the review.
in subject: typo "enable"
Will fix it.
This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
and
fxls8471. Almost all these devices have more than one event. Current driver
Hello,
fixes are always welcome, some comments regarding the patch
in subject: typo "enable"
> This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
> and
> fxls8471. Almost all these devices have more than one event. Current driver
> design
> hardcodes the event
Hello,
fixes are always welcome, some comments regarding the patch
in subject: typo "enable"
> This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
> and
> fxls8471. Almost all these devices have more than one event. Current driver
> design
> hardcodes the event
This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
and
fxls8471. Almost all these devices have more than one event. Current driver
design
hardcodes the event specific information, so only one event can be supported by
this
driver and current design doesn't have the
This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
and
fxls8471. Almost all these devices have more than one event. Current driver
design
hardcodes the event specific information, so only one event can be supported by
this
driver and current design doesn't have the
14 matches
Mail list logo