Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5.10.87 arm64 23 add greybus #266

Open
wants to merge 42 commits into
base: 5.10-arm64
Choose a base branch
from

Conversation

jadonk
Copy link
Member

@jadonk jadonk commented Jan 5, 2022

No description provided.

RobertCNelson and others added 30 commits December 28, 2021 20:13
Signed-off-by: Robert Nelson <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Add VTM bindings documentation. In the Voltage Thermal
Management Module(VTM), K3 J72XX supplies a voltage
reference and a temperature sensor feature that are gathered in the band
gap voltage and temperature sensor (VBGAPTS) module. The band
gap provides current and voltage reference for its internal
circuits and other analog IP blocks. The analog-to-digital
converter (ADC) produces an output value that is proportional
to the silicon temperature.

Signed-off-by: Keerthy <[email protected]>
VTM stands for Voltage Thermal Management

Signed-off-by: Keerthy <[email protected]>
VTM stands for Voltage Thermal Management

Signed-off-by: Keerthy <[email protected]>
Add VTM thermal support. In the Voltage Thermal Management
Module(VTM), K3 J72XX supplies a voltage reference and a temperature
sensor feature that are gathered in the band gap voltage and
temperature sensor (VBGAPTS) module. The band gap provides current and
voltage reference for its internal circuits and other analog IP
blocks. The analog-to-digital converter (ADC) produces an output value
that is proportional to the silicon temperature.

Currently reading temperatures only is supported.  There are no
active/passive cooling agent supported.

J721e SoCs have errata i2128: https://www.ti.com/lit/pdf/sprz455

The VTM Temperature Monitors (TEMPSENSORs) are trimmed during production,
with the resulting values stored in software-readable registers. Software
should use these  register values when translating the Temperature
Monitor output codes to temperature values.

It has an involved workaround. Software needs to read the error codes for
-40C, 30C, 125C from the efuse for each device & derive a new look up table
for adc to temperature conversion. Involved calculating slopes & constants
using 3 different straight line equations with adc refernce codes as the
y-axis & error codes in the x-axis.

-40C to 30C
30C to 125C
125C to 150C

With the above 2 line equations we derive the full look-up table to
workaround the errata i2128 for j721e SoC.

Tested temperature reading on J721e SoC & J7200 SoC.

Signed-off-by: Keerthy <[email protected]>
Signed-off-by: Robert Nelson <[email protected]>
Reference: v5.15.11
Signed-off-by: Robert Nelson <[email protected]>
This reverts commit 956b200.

Signed-off-by: Robert Nelson <[email protected]>
Reference: v5.15.11
Signed-off-by: Robert Nelson <[email protected]>
This Patch series is an update to the mikroBUS driver
with support for serdev devices and fixed regulator.

RFC v1 Patch : https://lkml.org/lkml/2020/7/24/518 .
The mikrobus driver is updated to add mikrobus ports from device-tree
overlays, the debug interfaces for adding mikrobus ports through sysFS
is removed, and the driver considers the extended usage of mikrobus
port pins from their standard purposes.

change log:
        v2: support for adding mikroBUS ports from DT overlays,
        remove debug sysFS interface for adding mikrobus ports,
        consider extended pin usage/deviations from mikrobus standard
        specifications,
        use greybus CPort protocol enum instead of new protcol enums
        Fix cases of wrong indendation, ignoring return values, freeing
        allocated resources in case of errors and other style suggestions
        in v1 review.

Signed-off-by: Vaishnav M A <[email protected]>
Currently,a serdev device driver can only be used with devices that are
nodes of a device tree, or are part of the ACPI table.id_table will be
used for devices that are not part of the device tree nor the ACPI table
(example: device on greybus gbphy created uart).

corresponding modalias field is introduced to name the driver to be
used with the device, required device(s) that are neither described
by device tree nor ACPI table.

serdev_device_uevent is also extended for modalias devices.

Signed-off-by: Ricardo Ribalda Delgado <[email protected]>
This patch allows file2alias to generate the proper module headers to
support serdev modalias drivers.

Eg:

root@qt5022:~# modinfo serdev:ttydev | grep alias
alias:          serdev:ttydev_serdev
alias:          serdev:ttydev

root@qt5022:~#
	cat /lib/modules/4.16.0-qtec-standard/modules.alias | grep serdev
alias serdev:ttydev_serdev serdev_ttydev
alias serdev:ttydev serdev_ttydev

Signed-off-by: Ricardo Ribalda Delgado <[email protected]>
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 5 times, most recently from 7cd1114 to bce804e Compare November 6, 2022 02:28
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 3 times, most recently from 3246d82 to 0bdfd59 Compare November 21, 2022 23:04
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 4 times, most recently from de529cb to 51996fd Compare December 8, 2022 01:40
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 3 times, most recently from 5f8a721 to 10f9081 Compare December 14, 2022 20:27
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 2 times, most recently from 532deb0 to 73b7baf Compare December 20, 2022 15:36
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 2 times, most recently from d4ab3f1 to 11ebcc0 Compare January 4, 2023 19:46
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 8 times, most recently from eb98542 to 6362564 Compare February 28, 2023 21:52
@RobertCNelson RobertCNelson force-pushed the 5.10-arm64 branch 2 times, most recently from 7436779 to 5a62bb1 Compare March 9, 2023 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants