-
Notifications
You must be signed in to change notification settings - Fork 17
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
Move shebang to the first line to allow scripts execution in systemd … #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MellanoxBSP
pushed a commit
that referenced
this pull request
Aug 17, 2020
…ionality and update licenses The patchset adds new features for the existing Mellanox systems. Patches #1-#2 update license to SPDX-License. Patch #3 moves header file out of x86 realm. Patch #4 adds support for word address space devices. Patch #5 extends mux number supported by driver. i2c: mux: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> platform/x86: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Move header file out of x86 realm Move out header file from include/linux/platform_data/x86/ to include/linux/platform_data/, since it does not depend on x86 architecture. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Extend driver to support word address space devices Extend driver to allow I2C routing control through CPLD devices with word address space. Till now only CPLD devices with byte address space have been supported. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com> i2c: mux: mlxcpld: Allow to extend mux number Allow to extend mux number supported by driver. Currently it is limited by eight, which is not enough for new coming Mellanox modular system with line cards, which require up to 64 mux support. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com>
MellanoxBSP
pushed a commit
that referenced
this pull request
Aug 17, 2020
…ionality and update licenses The patchset adds new features for the existing Mellanox systems. Patches #1-#2 update license to SPDX-License. Patch #3 moves header file out of x86 realm. Patch #4 adds support for word address space devices. Patch #5 extends mux number supported by driver. i2c: mux: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> platform/x86: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Move header file out of x86 realm Move out header file from include/linux/platform_data/x86/ to include/linux/platform_data/, since it does not depend on x86 architecture. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Extend driver to support word address space devices Extend driver to allow I2C routing control through CPLD devices with word address space. Till now only CPLD devices with byte address space have been supported. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com> i2c: mux: mlxcpld: Allow to extend mux number Allow to extend mux number supported by driver. Currently it is limited by eight, which is not enough for new coming Mellanox modular system with line cards, which require up to 64 mux support. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com>
sholeksandr
pushed a commit
that referenced
this pull request
Nov 12, 2020
…ionality and update licenses The patchset adds new features for the existing Mellanox systems. Patches #1-#2 update license to SPDX-License. Patch #3 moves header file out of x86 realm. Patch #4 adds support for word address space devices. Patch #5 extends mux number supported by driver. i2c: mux: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> platform/x86: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Move header file out of x86 realm Move out header file from include/linux/platform_data/x86/ to include/linux/platform_data/, since it does not depend on x86 architecture. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Extend driver to support word address space devices Extend driver to allow I2C routing control through CPLD devices with word address space. Till now only CPLD devices with byte address space have been supported. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com> i2c: mux: mlxcpld: Allow to extend mux number Allow to extend mux number supported by driver. Currently it is limited by eight, which is not enough for new coming Mellanox modular system with line cards, which require up to 64 mux support. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com>
sholeksandr
pushed a commit
that referenced
this pull request
Nov 12, 2020
…ionality and update licenses The patchset adds new features for the existing Mellanox systems. Patches #1-#2 update license to SPDX-License. Patch #3 moves header file out of x86 realm. Patch #4 adds support for word address space devices. Patch #5 extends mux number supported by driver. i2c: mux: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> platform/x86: mlxcpld: Update module license Update license to SPDX-License. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Move header file out of x86 realm Move out header file from include/linux/platform_data/x86/ to include/linux/platform_data/, since it does not depend on x86 architecture. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> i2c: mux: mlxcpld: Extend driver to support word address space devices Extend driver to allow I2C routing control through CPLD devices with word address space. Till now only CPLD devices with byte address space have been supported. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com> i2c: mux: mlxcpld: Allow to extend mux number Allow to extend mux number supported by driver. Currently it is limited by eight, which is not enough for new coming Mellanox modular system with line cards, which require up to 64 mux support. Signed-off-by: Vadim Pasternak <vadimp@mellanox.com> Reviewed-by: Michael Shych <michaelsh@mellanox.com>
vadimp-nvidia
added a commit
that referenced
this pull request
Feb 28, 2021
… and thermal Add line card thermal area registration and de-registration interfaces to thermal initialization/de-initialization flows. Add callback for line card thermal area activation and de-activation. These callbacks are to be invoked, when firmware indicates it got active or inactive state. When "active event" is received for particular line card, its thermal interfaces should be configured according to the configuration obtained from the firmware. When opposite "inactive event" is received all these interfaces should be removed. Each line card is associated with the relevant thermal area, which may contain thermal zones for cages and gearboxes found on this line card. For example thermal zone for module #9 located at line card #7 will have type: mlxsw-lc7-module9. And thermal zone for gearbox #2 located at line card #5 will have type: mlxsw-lc5-gearbox2. Add line card 'hwmon' registration and de-registration interfaces to 'hwmon' initialization/de-initialization flows. Add callback for line card 'hwmon' objects activation and de-activation. These callbacks are to be invoked, when firmware indicates it got active or inactive state. When "active event" is received for particular line card, its 'hwmon' interfaces should be configured according to the configuration obtained from the firmware. When opposite "inactive event" is received all these interfaces should be removed. Each line card is associated with the relevant 'hwmon' devices, which may contain thermal attributes for the cages and gearboxes found on this line card. For example cage temperature for module #9 located at line card #7 will be exposed by utility 'sensors' like: linecard#07 front panel 009: +32.0°C (crit = +70.0°C, emerg = +80.0°C) And temperature for gearbox #3 located at line card #5 will be exposed like: linecard#05 gearbox 003: +41.0°C (highest = +41.0°C) Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
vadimp-nvidia
added a commit
that referenced
this pull request
Feb 28, 2021
… and thermal Add line card thermal area registration and de-registration interfaces to thermal initialization/de-initialization flows. Add callback for line card thermal area activation and de-activation. These callbacks are to be invoked, when firmware indicates it got active or inactive state. When "active event" is received for particular line card, its thermal interfaces should be configured according to the configuration obtained from the firmware. When opposite "inactive event" is received all these interfaces should be removed. Each line card is associated with the relevant thermal area, which may contain thermal zones for cages and gearboxes found on this line card. For example thermal zone for module #9 located at line card #7 will have type: mlxsw-lc7-module9. And thermal zone for gearbox #2 located at line card #5 will have type: mlxsw-lc5-gearbox2. Add line card 'hwmon' registration and de-registration interfaces to 'hwmon' initialization/de-initialization flows. Add callback for line card 'hwmon' objects activation and de-activation. These callbacks are to be invoked, when firmware indicates it got active or inactive state. When "active event" is received for particular line card, its 'hwmon' interfaces should be configured according to the configuration obtained from the firmware. When opposite "inactive event" is received all these interfaces should be removed. Each line card is associated with the relevant 'hwmon' devices, which may contain thermal attributes for the cages and gearboxes found on this line card. For example cage temperature for module #9 located at line card #7 will be exposed by utility 'sensors' like: linecard#07 front panel 009: +32.0°C (crit = +70.0°C, emerg = +80.0°C) And temperature for gearbox #3 located at line card #5 will be exposed like: linecard#05 gearbox 003: +41.0°C (highest = +41.0°C) Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…services.