Add basic esp32p4 support

[playfulFence]

Submission Checklist 📝

• I have updated existing examples or added new ones (if applicable).
• I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
• My changes were added to the CHANGELOG.md in the proper section.
• I have added necessary changes to user code to the Migration Guide.
• My changes are in accordance to the esp-rs API guidelines

Extra:

• I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖

Description

For now, there're still some TODOs left. They'll be incrementally removed as p4 support grows. For example, for now some of checks in CI are off, some code sections and so on.

related to #2285

Testing

advanced_serial example, some more basic tests like:

//% CHIPS: esp32p4

#![no_std]
#![no_main]

use esp_backtrace as _;
use esp_hal::prelude::*;

#[entry]
fn main() -> ! {
    esp_println::println!("Hello world, from ESP32-P4 :)");

    loop {}
}

[jessebraham]

I don't think we want to include this in this release, so converting to draft for now.

[bugadani]

TBH I'd prefer not touching DMA for the P4.

[playfulFence]

I think there's nothing critical to have minor changes in terms of registers/fields management there, I think it can stay there

[bugadani]

I think there's nothing critical to have minor changes in terms of registers/fields management there, I think it can stay there

The P4 doesn't even have a single unified GDMA, it has two different ones. I doubt we'll use any of these additions in this form.

[bugadani]

Please undo this, FIXME is actually highlighted if you use the Todo Tree vscode plugin.

[jessebraham]

FIXME/TODO/NOTE are all pretty standard, plugin I use at least highlights all of those.

[bugadani]

Still, this change has no relevance for P4, and a FIXME better signals that something needs to be changed around these parts.

[playfulFence]

will be done

[MabezDev]

Thanks! I have some initial comments, mostly around the maintainability of adding more support in the future - we don't want to spend a bunch of time working on something only to realise the function that should be doing something is stubbed out to do nothing :D.

I'll dig out my P4 rev1 board and try the examples soon.

[MabezDev]

Can we just cfg away DMA changes (i.e remove gdma from metadata)? We won't have a need for it for some time, and DMA on P4 is going to be complicated.

[playfulFence]

if that works: #2466 (comment)

gdma will be temporarily removed from metadata

[playfulFence]

Regarding dma stuff: currently we have a lot of drivers which are tightly coupled to dma. UART is one of them, create_peripheral macro as well, so as soon as you exclude gdma from metadata, you'll immediately get an unknown amount of errors.

[bugadani]

Yeah let's have those errors, I'll move PeripheralMarker to a better place. Alternatively, you could define an axi_gdma and ahb_gdma symbol pair, and cfg-enable dma for those without gdma/pdma parts.