-
Notifications
You must be signed in to change notification settings - Fork 76
Refactor/relacement names #516
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
base: master
Are you sure you want to change the base?
Refactor/relacement names #516
Conversation
All platforms currently use __PART_FAMILY_NAME__ to point at an explicit device name. Update this platform to match. Signed-off-by: Randolph Sapp <rs@ti.com>
Replace all instances of __PART_FAMILY_DEVICE_NAMES__ with __PART_FAMILY_NAME__ since the two are equivalent. Signed-off-by: Randolph Sapp <rs@ti.com>
Remove the __PART_FAMILY_DEVICE_NAMES__ replacement definition since it is no longer used. Signed-off-by: Randolph Sapp <rs@ti.com>
jmenti
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making sure there is no bug in the variable you are modifying, but other than that, this looks good to me
| ------------ | ||
|
|
||
| In today's fast-paced automotive industry, the ability to achieve quick processor boot times is more crucial than ever. This guide will walk you through the necessary steps and considerations for achieving faster boot times on |__PRODUCT_LINE_NAME__| |__PART_FAMILY_DEVICE_NAMES__| devices. From adjusting configurations to implementing best practices, you'll gain the insights needed to deliver a seamless, responsive user experience in your automotive applications. By implementing specific modifications, the default SDK offering can be optimized to boot much faster. | ||
| In today's fast-paced automotive industry, the ability to achieve quick processor boot times is more crucial than ever. This guide will walk you through the necessary steps and considerations for achieving faster boot times on |__PRODUCT_LINE_NAME__| |__PART_FAMILY_NAME__| devices. From adjusting configurations to implementing best practices, you'll gain the insights needed to deliver a seamless, responsive user experience in your automotive applications. By implementing specific modifications, the default SDK offering can be optimized to boot much faster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a bug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you think this is a bug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if the diff here is tricking me, but:
considerations for achieving faster boot times on |PRODUCT_LINE_NAME| |
PART_FAMILY_NAME|
is the second variable missing the leading pipe?
| | Range 2 (MCU_PORz to SBL_start): | ||
| | MCU_PORz is the Power-On-Reset pin that is set HIGH as soon as the PMIC powers the voltage rails. This can be probed using Pin #28 on the MCU Header (J11) of the |__PART_FAMILY_DEVICE_NAMES__|. All pins are automatically set HIGH at this point. | ||
| | MCU_PORz is the Power-On-Reset pin that is set HIGH as soon as the PMIC powers the voltage rails. This can be probed using Pin #28 on the MCU Header (J11) of the |__PART_FAMILY_NAME__|. All pins are automatically set HIGH at this point. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question here.
|
Marking this as blocked until the current release's influx of PRs has settled down. |
refactor(names): remove PART_FAMILY_DEVICE_NAMES
Remove the PART_FAMILY_DEVICE_NAMES replacement definition since it is no
longer used.
Signed-off-by: Randolph Sapp rs@ti.com
refactor(names): use shorter replacement name
Replace all instances of PART_FAMILY_DEVICE_NAMES with
PART_FAMILY_NAME since the two are equivalent.
Signed-off-by: Randolph Sapp rs@ti.com
fix(TDA4VM): set PART_FAMILY_NAME to device
All platforms currently use PART_FAMILY_NAME to point at an explicit
device name. Update this platform to match.
Signed-off-by: Randolph Sapp rs@ti.com
Opening as a draft for now as there are other cleanup efforts I assume will clash with this currently.