aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/spi/spi-samsung.txt
diff options
context:
space:
mode:
authorSiarhei Vishniakou <svv@google.com>2022-07-08 21:59:23 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2022-07-08 22:02:00 -0700
commit2a96271fb66c499e4a89d76a89d3d01170c10bef (patch)
tree6c9b0c307da7c342dc5e6fb754d59057aa684a22 /Documentation/devicetree/bindings/spi/spi-samsung.txt
parentInput: goodix - call acpi_device_fix_up_power() in some cases (diff)
downloadlinux-dev-2a96271fb66c499e4a89d76a89d3d01170c10bef.tar.xz
linux-dev-2a96271fb66c499e4a89d76a89d3d01170c10bef.zip
Input: document the units for resolution of size axes
Today, the resolution of size axes is not documented. As a result, it's not clear what the canonical interpretation of this value should be. On Android, there is a need to calculate the size of the touch ellipse in physical units (millimeters). After reviewing linux source, it turned out that most of the existing usages are already interpreting this value as "units/mm". This documentation will make it explicit. This will help device implementations with correctly following the linux specs, and will ensure that the devices will work on Android without needing further customized parameters for scaling of major/minor values. Signed-off-by: Siarhei Vishniakou <svv@google.com> Reviewed-by: Jeff LaBundy <jeff@labundy.com> Link: https://lore.kernel.org/r/20220520084514.3451193-1-svv@google.com Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'Documentation/devicetree/bindings/spi/spi-samsung.txt')
0 files changed, 0 insertions, 0 deletions