drivers/pcie: Change pcie_get_mbar() to return size and flags

[maxbachmann]

currently pcie_get_mbar only returns the physical address.
This changes the function to return the size of the mbar and
the flags (IO Bar vs MEM BAR).

This implements #26491. I did decide to change the existing function instead of adding another function to retrieve the size for the following reasons:

1. in most of the cases both size and physical address are required anyways
2. The flags might be interesting aswell e.g. to select IO Bar vs Mem Bar

This fixes the macros for the use with IO Bars

[tbursztyka]

I don't know if we still enforce 80 chars limit, but in doubt please do.

I needed something like that recently, in #29479 but getting both adress and size at once makes sense.

[tbursztyka]

Actually, about differentiating IO and MEM. I don't know if that's relevant anymore since no platform so far make use of IO stuff. We only needed it for galileo board back in the days.

[maxbachmann]

Actually, about differentiating IO and MEM. I don't know if that's relevant anymore since no platform so far make use of IO stuff. We only needed it for galileo board back in the days.

I personally only care about this info, since e.g. The Realtek 8111G Controller has the following bars

1. address=0xE000 size=256 type=IO
2. address=0x91404000 size=4k type=MEM (64 bit)
3. address=0x91400000 size=16k type=MEM (64 bit)

I want to use the first MEM Bar. So I either need this info, or since as you said nobody uses the IO stuff, we could skip all IO Bars aswell.

[tbursztyka]

I want to use the first MEM Bar. So I either need this info, or since as you said nobody uses the IO stuff, we could skip all IO Bars aswell.
Yes somes devices expose both types for legacy support, but the MEM is the way to go in zephyr so far, so skipping IO bars would be fine

[maxbachmann]

Yes somes devices expose both types for legacy support, but the MEM is the way to go in zephyr so far, so skipping IO bars would be fine

Ok I skip I/O Bars now aswell

[tbursztyka]

@jhedberg Can you merge this one? I need that function for msi-x and ivshmem

[tbursztyka]

Maybe proposing a function in parallel to the existing one would have been more aligned with https://docs.zephyrproject.org/latest/development_process/api_lifecycle.html