[GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Dinh Nguyen]

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_dts_updates_for_v7.4

for you to fetch changes up to 1c4d22949a77d82505188bf36a4bcae0cbdf699e:

  arm64: dts: altera: Move all SoCFPGA files to dts/altera (2026-10-08 11:25:18 -0500)

----------------------------------------------------------------
SoCFPGA DTS updates for v7.4
dt-bindings:
- Add the SOCDK eMMC and TSN config2 boards based on Agilex5
- Update the interrupts spec for the Stratix10 Service Layer
dts:
- Agilex5
   - Add FPGA manager, region, and USB3.1 node in the base DTSI
   - Add SD/eMMC on the SoCDK OOBE card
   - Add the SoCDK eMMC daughter board
   - Add support for the debug daughter card
   - Add support for the  SoCDK TSN Config2 board
- Add SDM interrupts for Agilex and Stratix10
- Move all Altera SoCFPGA dts files to dts/altera

----------------------------------------------------------------
Adrian Ng Ho Yin (3):
      arm64: dts: intel: agilex5: add USB3.1 controller node
      arm64: dts: intel: agilex5: remove usb0 in Agilex5 SoCDK
      arm64: dts: agilex5: add support for debug daughter card

Dinh Nguyen (3):
      arm64: dts: socfpga: agilex5: add FPGA manager and region nodes
      arm64: dts: socfpga: agilex5: Add SoCDK TSN Config2 board
      arm64: dts: altera: Move all SoCFPGA files to dts/altera

Mahesh Rao (3):
      dt-bindings: firmware: Add interrupt specification for Intel Stratix 10 Service Layer
      dts: stratix10: Add support for SDM mailbox interrupt for Intel Stratix10 SoCFPGA
      dts: agilex: Add support for SDM mailbox interrupt for Intel Agilex SoCFPGA

Nazim Amirul (1):
      dt-bindings: arm: altera: Add Agilex5 SoCDK TSN Config2 board

Tanmay Kathpalia (4):
      arm64: dts: agilex5: add SD/eMMC host controller
      arm64: dts: agilex5: enable SD card on SOCDK OOBE card
      dt-bindings: arm: altera: add Agilex5 SOCDK eMMC board variant
      arm64: dts: agilex5: add SOCDK eMMC daughter board

 Documentation/devicetree/bindings/arm/altera.yaml  |   2 +
 .../bindings/firmware/intel,stratix10-svc.yaml     |  10 ++
 arch/arm64/boot/dts/altera/Makefile                |  14 +-
 .../boot/dts/{intel => altera}/socfpga_agilex.dtsi |   2 +
 .../{intel => altera}/socfpga_agilex3_socdk.dts    |   0
 .../dts/{intel => altera}/socfpga_agilex5.dtsi     |  61 +++++++++
 .../boot/dts/altera/socfpga_agilex5_socdk.dts      | 146 +++++++++++++++++++++
 .../socfpga_agilex5_socdk_013b.dts                 |   0
 .../dts/altera/socfpga_agilex5_socdk_debug.dts     | 121 +++++++++++++++++
 .../boot/dts/altera/socfpga_agilex5_socdk_emmc.dts | 123 +++++++++++++++++
 .../socfpga_agilex5_socdk_modular.dts              |   0
 .../socfpga_agilex5_socdk_nand.dts                 |   0
 .../socfpga_agilex5_socdk_tsn_cfg2.dts}            |  40 ++++--
 .../dts/{intel => altera}/socfpga_agilex72.dtsi    |   0
 .../{intel => altera}/socfpga_agilex72_socdk.dts   |   0
 .../{intel => altera}/socfpga_agilex7m_socdk.dts   |   0
 .../dts/{intel => altera}/socfpga_agilex_n6000.dts |   0
 .../dts/{intel => altera}/socfpga_agilex_socdk.dts |   0
 .../socfpga_agilex_socdk_emmc.dts                  |   0
 .../socfpga_agilex_socdk_nand.dts                  |   0
 .../dts/{intel => altera}/socfpga_n5x_socdk.dts    |   0
 arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi  |   4 +
 arch/arm64/boot/dts/intel/Makefile                 |  12 --
 23 files changed, 510 insertions(+), 25 deletions(-)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex.dtsi (99%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex3_socdk.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex5.dtsi (93%)
 create mode 100644 arch/arm64/boot/dts/altera/socfpga_agilex5_socdk.dts
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex5_socdk_013b.dts (100%)
 create mode 100644 arch/arm64/boot/dts/altera/socfpga_agilex5_socdk_debug.dts
 create mode 100644 arch/arm64/boot/dts/altera/socfpga_agilex5_socdk_emmc.dts
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex5_socdk_modular.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex5_socdk_nand.dts (100%)
 rename arch/arm64/boot/dts/{intel/socfpga_agilex5_socdk.dts => altera/socfpga_agilex5_socdk_tsn_cfg2.dts} (73%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex72.dtsi (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex72_socdk.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex7m_socdk.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex_n6000.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex_socdk.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex_socdk_emmc.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_agilex_socdk_nand.dts (100%)
 rename arch/arm64/boot/dts/{intel => altera}/socfpga_n5x_socdk.dts (100%)

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[patchwork-bot+linux-soc]

Hello:

This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Thu,  8 Oct 2026 11:47:35 -0500 you wrote:
> The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
> 
>   Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_dts_updates_for_v7.4
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/2] SoCFPGA DTS updates for v7.4
    (no matching commit)
  - [GIT,PULL,2/2] MAINTAINERS: socfpga: update for v7.4
    https://git.kernel.org/soc/soc/c/41eb191bcd8f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Dinh Nguyen]

Hi Arnd,

On 10/13/26 11:10, patchwork-bot+linux-soc@kernel.org wrote:
>    - [GIT,PULL,1/2] SoCFPGA DTS updates for v7.4
>      (no matching commit)

I see that the bot has pull in the 2/2 of PR, but something may have 
gone wrong with the PR 1/2?

I may have done something wrong? Can you please take a look?

Thanks,
Dinh

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Arnd Bergmann]

On Wed, Oct 14, 2026, at 01:33, Dinh Nguyen wrote:
> Hi Arnd,
>
> On 10/13/26 11:10, patchwork-bot+linux-soc@kernel.org wrote:
>>    - [GIT,PULL,1/2] SoCFPGA DTS updates for v7.4
>>      (no matching commit)
>
> I see that the bot has pull in the 2/2 of PR, but something may have 
> gone wrong with the PR 1/2?
>
> I may have done something wrong? Can you please take a look?

We tend to pull in similar branches from different submitters together,
I only got through the defconfig, drivers and arm32 branches yesterday,
the DT branches should get there in the next few days. It's a bit late
because of lpc, but unless something shows up it should be there in
the next two days.

      Arnd

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Dinh Nguyen]

On 10/14/26 02:06, Arnd Bergmann wrote:
> On Wed, Oct 14, 2026, at 01:33, Dinh Nguyen wrote:
>> Hi Arnd,
>>
>> On 10/13/26 11:10, patchwork-bot+linux-soc@kernel.org wrote:
>>>     - [GIT,PULL,1/2] SoCFPGA DTS updates for v7.4
>>>       (no matching commit)
>>
>> I see that the bot has pull in the 2/2 of PR, but something may have
>> gone wrong with the PR 1/2?
>>
>> I may have done something wrong? Can you please take a look?
> 
> We tend to pull in similar branches from different submitters together,
> I only got through the defconfig, drivers and arm32 branches yesterday,
> the DT branches should get there in the next few days. It's a bit late
> because of lpc, but unless something shows up it should be there in
> the next two days.
> 
>        Arnd

Sorry to bother you guys again, but I still don't see the commits in 
this PR in any of the soc branches. Please let me know if there's any I 
need to do.

Thanks,
Dinh

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Arnd Bergmann]

On Mon, Oct 19, 2026, at 15:21, Dinh Nguyen wrote:
> On 10/14/26 02:06, Arnd Bergmann wrote:
>> On Wed, Oct 14, 2026, at 01:33, Dinh Nguyen wrote:
>>>
>>> I see that the bot has pull in the 2/2 of PR, but something may have
>>> gone wrong with the PR 1/2?
>>>
>>> I may have done something wrong? Can you please take a look?
>> 
>> We tend to pull in similar branches from different submitters together,
>> I only got through the defconfig, drivers and arm32 branches yesterday,
>> the DT branches should get there in the next few days. It's a bit late
>> because of lpc, but unless something shows up it should be there in
>> the next two days.
>
> Sorry to bother you guys again, but I still don't see the commits in 
> this PR in any of the soc branches. Please let me know if there's any I 
> need to do.

Hi Dinh,

Sorry for missing this: Alexandre pointed out that when he looked
at the branch it was not part of linux-next and did not pull it,
and I assumed that he had notified you about it when I did the
final merges for 7.4.

I see that you have a for-next branch with a different set of commit
IDs but overlapping contents. Can you explain what is going on?
I normall expect that whatever you send for inclusion in the soc
tree has seen some time in linux-next using the exact git commits.

I fear that at this point it is a little late to take either
version of the branch, but it would be nice if you could see
if there are important changes (not new features) that you can rebase
and send for the first set of fixes that can still make it into -rc1.

       Arnd

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Alexandre Belloni]

On 21/10/2026 18:46:39+0200, Arnd Bergmann wrote:
> On Mon, Oct 19, 2026, at 15:21, Dinh Nguyen wrote:
> > On 10/14/26 02:06, Arnd Bergmann wrote:
> >> On Wed, Oct 14, 2026, at 01:33, Dinh Nguyen wrote:
> >>>
> >>> I see that the bot has pull in the 2/2 of PR, but something may have
> >>> gone wrong with the PR 1/2?
> >>>
> >>> I may have done something wrong? Can you please take a look?
> >> 
> >> We tend to pull in similar branches from different submitters together,
> >> I only got through the defconfig, drivers and arm32 branches yesterday,
> >> the DT branches should get there in the next few days. It's a bit late
> >> because of lpc, but unless something shows up it should be there in
> >> the next two days.
> >
> > Sorry to bother you guys again, but I still don't see the commits in 
> > this PR in any of the soc branches. Please let me know if there's any I 
> > need to do.
> 
> Hi Dinh,
> 
> Sorry for missing this: Alexandre pointed out that when he looked
> at the branch it was not part of linux-next and did not pull it,
> and I assumed that he had notified you about it when I did the
> final merges for 7.4.
> 
> I see that you have a for-next branch with a different set of commit
> IDs but overlapping contents. Can you explain what is going on?
> I normall expect that whatever you send for inclusion in the soc
> tree has seen some time in linux-next using the exact git commits.
> 
> I fear that at this point it is a little late to take either
> version of the branch, but it would be nice if you could see
> if there are important changes (not new features) that you can rebase
> and send for the first set of fixes that can still make it into -rc1.
> 

My mistake, I forgot to notify, I wanted to sort out whether the new
dtbs_check warnings I had where due to the renaming or had another
reason.

After removing some false positives, the issues were:

cbce4a0dacb6: arm64: dts: intel: agilex5: add USB3.1 controller node
      + /soc@0/bus@11000000/usb@0: failed to match any schema with compatible: ['altr,agilex5-dwc3']
        from arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi:534 (dtsi)

The issue here is that GKH never took the related dt-bindings, I
believe because Krzysztof had comments on it.

29f11fb83ad5: arm64: dts: agilex5: add support for debug daughter card
      + /soc@0/spi@10da4000/eeprom@0: failed to match any schema with compatible: ['microchip,25aa128', 'atmel,at25']
        from arch/arm64/boot/dts/altera/socfpga_agilex5_socdk_debug.dts:101 (dts)


It seems that there is a different version of the branch in linux-next.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Dinh Nguyen]

On 10/21/26 13:26, Alexandre Belloni wrote:
> On 21/10/2026 18:46:39+0200, Arnd Bergmann wrote:
>> On Mon, Oct 19, 2026, at 15:21, Dinh Nguyen wrote:
>>> On 10/14/26 02:06, Arnd Bergmann wrote:
>>>> On Wed, Oct 14, 2026, at 01:33, Dinh Nguyen wrote:
>>>>>
>>>>> I see that the bot has pull in the 2/2 of PR, but something may have
>>>>> gone wrong with the PR 1/2?
>>>>>
>>>>> I may have done something wrong? Can you please take a look?
>>>>
>>>> We tend to pull in similar branches from different submitters together,
>>>> I only got through the defconfig, drivers and arm32 branches yesterday,
>>>> the DT branches should get there in the next few days. It's a bit late
>>>> because of lpc, but unless something shows up it should be there in
>>>> the next two days.
>>>
>>> Sorry to bother you guys again, but I still don't see the commits in
>>> this PR in any of the soc branches. Please let me know if there's any I
>>> need to do.
>>
>> Hi Dinh,
>>
>> Sorry for missing this: Alexandre pointed out that when he looked
>> at the branch it was not part of linux-next and did not pull it,
>> and I assumed that he had notified you about it when I did the
>> final merges for 7.4.
>>
>> I see that you have a for-next branch with a different set of commit
>> IDs but overlapping contents. Can you explain what is going on?
>> I normall expect that whatever you send for inclusion in the soc
>> tree has seen some time in linux-next using the exact git commits.

Yes, I was aware of the linux-next requirement and have been placing the 
commits into the for-next branch. I was cherry-picking the commits into 
my for-next branch. I didn't realized you needed to preserve the same 
commit IDs as well. I will change my process to keep the same commit IDs 
going forward.

>>
>> I fear that at this point it is a little late to take either
>> version of the branch, but it would be nice if you could see
>> if there are important changes (not new features) that you can rebase
>> and send for the first set of fixes that can still make it into -rc1.
>>

Ok, will do.
> 
> My mistake, I forgot to notify, I wanted to sort out whether the new
> dtbs_check warnings I had where due to the renaming or had another
> reason.
> 
> After removing some false positives, the issues were:
> 
> cbce4a0dacb6: arm64: dts: intel: agilex5: add USB3.1 controller node
>        + /soc@0/bus@11000000/usb@0: failed to match any schema with compatible: ['altr,agilex5-dwc3']
>          from arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi:534 (dtsi)
> 
> The issue here is that GKH never took the related dt-bindings, I
> believe because Krzysztof had comments on it.

I saw that the bindings got the Reviewed-by:[1] Krzysztof so I went 
ahead and applied the DTS.
> 
> 29f11fb83ad5: arm64: dts: agilex5: add support for debug daughter card
>        + /soc@0/spi@10da4000/eeprom@0: failed to match any schema with compatible: ['microchip,25aa128', 'atmel,at25']
>          from arch/arm64/boot/dts/altera/socfpga_agilex5_socdk_debug.dts:101 (dts)
> 
> 
> It seems that there is a different version of the branch in linux-next.
> 

I will address this in the next release.

Thanks,
Dinh


[1] 
https://lore.kernel.org/all/20260911-nondescript-toucan-of-perspective-6bd8bd@quoll/

Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4

[Arnd Bergmann]

On Wed, Oct 21, 2026, at 22:33, Dinh Nguyen wrote:
> On 10/21/26 13:26, Alexandre Belloni wrote:
>> On 21/10/2026 18:46:39+0200, Arnd Bergmann wrote:
>>> On Mon, Oct 19, 2026, at 15:21, Dinh Nguyen wrote:
>>>
>>> Sorry for missing this: Alexandre pointed out that when he looked
>>> at the branch it was not part of linux-next and did not pull it,
>>> and I assumed that he had notified you about it when I did the
>>> final merges for 7.4.
>>>
>>> I see that you have a for-next branch with a different set of commit
>>> IDs but overlapping contents. Can you explain what is going on?
>>> I normall expect that whatever you send for inclusion in the soc
>>> tree has seen some time in linux-next using the exact git commits.
>
> Yes, I was aware of the linux-next requirement and have been placing the 
> commits into the for-next branch. I was cherry-picking the commits into 
> my for-next branch. I didn't realized you needed to preserve the same 
> commit IDs as well. I will change my process to keep the same commit IDs 
> going forward.

Thanks! There are two reasons for requiring the exact commits here:

 - we all rely on scripts to check if commits are merged already,
   and those break if the changesets are different.

 - once the branch gets merged into the soc tree, it may conflict
   with the same patches in another branch, at least if there are
   multiple patches touching the same lines.

      Arnd