-
Notifications
You must be signed in to change notification settings - Fork 78
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
linux-iot2050: Update to v6.1.54-cip6[-rt3] #491
Conversation
Better to add this information to the commit message body, so later people could easily get this information without opening this PR. |
4c60b1a
to
f965ca2
Compare
Let's split the commit into 2, first adding 6.1 then dropping 5.10. Makes them a bit more handy. |
791d964
to
7ad363a
Compare
But none of those patches in the commit log are part of this MR. I don't think this makes sense to mention here. I'm way more interested in the line where backporting stops and SDK or own patches start. Please clarify that. |
OTOH, when reading "Fix NULL pointer deference" more than once in that list of to-be-integrated patches: Are none of those fixes relevant for the patches we already carry, ie. are they only addressing issues from that extra patch list? |
Regarding the line, that is what TI is currently addressing in the mailing lists, specifically in 1, meaning that everything below that line is still only present in the SDK and my guess is that it will be mainlined after the features in 1 are added. The |
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.
We don't need this, neither functionally (it's for AM64) nor to make the application of succeeding patches simpler. Same for 0033.
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.
Let's move this back-to-back with patch 0071.
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.
There is 9d2e77ff2bd3b94c930a1f5b75abada7e196fa6d in upstream containing this. You likely picked the wrong source here, possible also for patch 59.
7ad363a
to
e3ebbfb
Compare
Signed-off-by: Nikhil Devshatwar <[email protected]> | ||
Signed-off-by: Vignesh Raghavendra <[email protected]> | ||
Tested-by: Praneeth Bajjuri <[email protected]> | ||
[Taken from TI 6.1 SDK] |
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 don't find this in 6.1 anymore, only in 5.10.
Needs rebasing over master but looks good otherwise (except for that annotation detail). |
28ef458
to
4bafddc
Compare
1efd85e
to
4036ffb
Compare
@@ -444,7 +437,6 @@ CONFIG_REGULATOR_GPIO=y | |||
CONFIG_REGULATOR_HI6421V530=y | |||
CONFIG_REGULATOR_MAX77620=y | |||
CONFIG_REGULATOR_PALMAS=y | |||
CONFIG_REGULATOR_PWM=y |
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.
Interesting that this automatically dropped off. But checking our DT, I don't see we ever needed it.
CONFIG_DRM=y | ||
CONFIG_DRM_I2C_NXP_TDA998X=y | ||
CONFIG_DRM_PANEL_SIMPLE=y | ||
CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS=y |
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 remark for this: correctly dropped, we don't have this. Did you check manually?
CONFIG_FRAMEBUFFER_CONSOLE=y | ||
CONFIG_LOGO=y | ||
# CONFIG_LOGO_LINUX_MONO is not set | ||
# CONFIG_LOGO_LINUX_VGA16 is not set |
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.
These look suspicious, though. Aren't we losing the framebuffer console this way? Did you test?
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.
CONFIG_FB=y
now needed. Display remained black.
@@ -490,11 +470,9 @@ CONFIG_SND_SOC_DAVINCI_MCASP=y | |||
CONFIG_SND_SOC_AK4613=m | |||
CONFIG_SND_SOC_PCM3168A_I2C=m | |||
CONFIG_SND_SOC_TLV320AIC31XX=m | |||
CONFIG_SND_SOC_TLV320AIC3X=m |
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.
This driver was split into I2C and SPI attached ones. We may have used the I2C version before.
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.
...or this was simply inherited from the EMV defconfig which has extensions we don't have.
@@ -506,9 +484,6 @@ CONFIG_USB_OHCI_HCD=m | |||
CONFIG_USB_OHCI_HCD_PLATFORM=m | |||
CONFIG_USB_ACM=m | |||
CONFIG_USB_STORAGE=m | |||
CONFIG_USB_CDNS3=m | |||
CONFIG_USB_CDNS3_GADGET=y | |||
CONFIG_USB_CDNS3_HOST=y |
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.
These were most likely EVM inherited, the AM65 does not use this.
CONFIG_NEW_LEDS=y | ||
CONFIG_LEDS_CLASS=y | ||
CONFIG_LEDS_GPIO=y | ||
CONFIG_LEDS_PWM=y |
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.
indeed, unused.
CONFIG_TI_SCI_PM_DOMAINS=y | ||
CONFIG_TI_PRUSS=y | ||
CONFIG_EXTCON_PALMAS=m | ||
CONFIG_EXTCON_USB_GPIO=m | ||
CONFIG_MEMORY=y | ||
CONFIG_IIO=y | ||
CONFIG_TI_AM335X_ADC=m | ||
CONFIG_PWM_TIECAP=y | ||
CONFIG_PWM_TIEHRPWM=y |
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.
These two seems used.
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.
CONFIG_PWM=y
now needed.
Move PRUETH driver from module to built-in in order to avoid a probing race condition. CONFIG_FB is no longer auto-selected. Enable it to preserve framebuffer support. CONFIG_PWM needs to be explicitly enabled with the newer kernel. Finally, CONFIG_RT_GROUP_SCHED must be disabled for the RT kernel as it is officially incompatible and breaks requesting RT scheduling policies. Signed-off-by: Diogo Ivo <[email protected]> [Jan: add phys_port_name icssg-prueth patch, fix defconfig] Signed-off-by: Jan Kiszka <[email protected]>
Signed-off-by: Diogo Ivo <[email protected]>
Regenerated via oldefconfig, followed by savedefconfig. Signed-off-by: Diogo Ivo <[email protected]> [Jan: rebased and refreshed] Signed-off-by: Jan Kiszka <[email protected]>
4036ffb
to
d9b46fc
Compare
@diogo-ivo I've patched some issues, and the result looks now good to me. Still not understood is the probing race, but I noticed that it is gone with 6.6-rcX. We might be missing some patch. @BaochengSu I think we can merge this and move forward with testing. |
Sure, let's move forward |
This PR includes all patches 5.10 except some prueth functionality still being upstreamed by TI, namely:
------------------------------- Current upstream attempts stop here--------------------------------------------