This patch fixes by detaching the event related information fromI think its not necessary as we only have Freefall and Transient events for now.
chip_info struct,
event configuration registersand based on channel type and event direction the corresponding
read/write callbacks.are picked dynamically. Hence multiple events can be handled in
which chip can have which event(s)?I am planning to add 'supported events' field in
struct mma_chip_info which indicates which chip can have which events.
During initialization in 'mma_chip_info_table' would set this
'supported events' field for each chip.
But I wonder should I add those changes as part of this patch?
is it necessary or can it be documentation?
Sure I will send v3 patch, should I use '--in-reply-to' option of git send-email to send v3 patch as reply to
And this patch should have been called "v2". please include a persistent version history to v3 of this patch.
is it necessary or can it be documentation?chip_info struct,This patch fixes by detaching the event related information from
event configuration registersand based on channel type and event direction the corresponding
read/write callbacks.are picked dynamically. Hence multiple events can be handled in
which chip can have which event(s)?I am planning to add 'supported events' field in
struct mma_chip_info which indicates which chip can have which events.
During initialization in 'mma_chip_info_table' would set this
'supported events' field for each chip.
But I wonder should I add those changes as part of this patch?
And this patch should have been called "v2". please include a persistent version history to v3 of this patch.