-
Notifications
You must be signed in to change notification settings - Fork 919
Rpi 6.6.y arm64 defconfigs #2816
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
Conversation
nunojsa
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.
This would also be the time where you could add the CI jobs for these new two configs. Another note is for commit subjects. No need for the "drivers:" prefix
|
|
||
| pwmchip_remove(&pc->chip); | ||
|
|
||
| return 0; |
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 patch looks like is updating the driver not adding it?
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 cherry picked the (only) commit adding the driver on the rpi linux 6.13 branch. Should I change the description? maybe also squash this and the next commit that fixes this driver to match the pwm interface?
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.
Since it seems we cannot cherry-pick individual patches maybe just squash all patches and change the description to say that we need to modify the driver to match APIs A and B
|
v1 -> v2: |
7f5eddb to
5d1b038
Compare
|
v2 -> v3: |
|
I know that the rpi1.c files are not maintained by us, but the reason for the auto inferred ci to be failing is because the rpi1.c depends on symbol CONFIG_PCI_MSI to define the pci_msi_* methods, but never sets so. Opened a pr at raspberrypi/linux#6891 about was fixed last week at raspberrypi/linux@564a5ad |
nunojsa
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.
It seems that CI needs some fixing
|
|
||
| pwmchip_remove(&pc->chip); | ||
|
|
||
| return 0; |
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.
Since it seems we cannot cherry-pick individual patches maybe just squash all patches and change the description to say that we need to modify the driver to match APIs A and B
5d1b038 to
46f0968
Compare
|
v3 -> v4: |
Update driver to match both the current pwm and the platform_driver interface. Signed-off-by: Alisa-Dariana Roman <[email protected]>
Update driver to match the rpi 6.13 linux repository analog driver. Since pwm interface was backported to this version, this driver was no longer matching the interface. Also match the current platform_driver interface. Signed-off-by: Alisa-Dariana Roman <[email protected]>
Add module import statements for drivers. The build was failing because of missing symbols. Signed-off-by: Alisa-Dariana Roman <[email protected]>
There is already the driver in drivers/mfd/rp1.ko, so having drivers/firmware/rp1.ko can cause issues when using modinfo and similar, and we can get errors with "Module rp1 is already loaded" when trying to load it. Rename the module so that the name is unique. Signed-off-by: Dave Stevenson <[email protected]> (cherry picked from commit 564a5ad)
46f0968 to
c3eb47b
Compare
|
v4 -> v5: Also, should I mention somewhere the name and email of the person who made the drivers updates on the rpi linux repo? |
PR Description
Add arm64 ADI defconfigs for RPi4 and RPi5.
PR Type
PR Checklist