We've moved away from using platform data in our project because it's
clunky, and because we implemented the config loading that's similar
to what you submitted elsewhere in this series.
Furthermore, for our ARM projects specifically, we are using flattened
device trees to describe our board and i
Benson Leung wrote:
> This is disappointing that Atmel decided to change the bootloader
> address scheme for the 1664S family. Unfortunately, this ifdef won't
> work for situations where there are more than one Atmel device of a
> different kind on a system using this same driver.
>
> For the C
This is disappointing that Atmel decided to change the bootloader
address scheme for the 1664S family. Unfortunately, this ifdef won't
work for situations where there are more than one Atmel device of a
different kind on a system using this same driver.
For the Chromebook Pixel, we use the same at
The mXT1664S family chips use different mappings for bootloader addresses.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index
4 matches
Mail list logo
