Hi Guenter:
>> Change boot mode trigger parameter of Raydium firmware update.
>>
>That is a bit vague. What is changed to what, and why ?
>In other words, what prevents someone else from changing it back to
>the old value, using the same description ?
This bit control erase type as doing firmware update. We want just reserve more infomation after pass through production line. This's convenient
for debug, so that it's okay as some one use old version.
>> Signed-off-by: jeffrey.lin <jeffrey.lin@xxxxxxxxxx>
>> ---
>> drivers/input/touchscreen/raydium_i2c_ts.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/input/touchscreen/raydium_i2c_ts.c b/drivers/input/touchscreen/raydium_i2c_ts.c
>> index a99fb5cac5a0..8a81257634ba 100644
>> --- a/drivers/input/touchscreen/raydium_i2c_ts.c
>> +++ b/drivers/input/touchscreen/raydium_i2c_ts.c
>> @@ -450,7 +450,7 @@ static bool raydium_i2c_boot_trigger(struct i2c_client *client)
>> { 0x08, 0x04, 0x09, 0x00, 0x50, 0xA5 },
>> { 0x08, 0x0C, 0x09, 0x00, 0x50, 0x00 },
>> { 0x06, 0x01, 0x00, 0x00, 0x00, 0x00 },
>> - { 0x02, 0xA2, 0x00, 0x00, 0x00, 0x00 },
>> + { 0x02, 0xA1, 0x00, 0x00, 0x00, 0x00 },
>> };
Thanks.
Jeffrey
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
