public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: "Ivan T. Ivanov" <iivanov@suse.de>
Cc: "Matthias Brugger" <mbrugger@suse.com>,
	"Peter Robinson" <pbrobinson@gmail.com>,
	"Dmitry Malkin" <dmitry@bedrocksystems.com>,
	"Thomas Fitzsimmons" <fitzsim@fitzsim.org>,
	"Peng Fan" <peng.fan@nxp.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Anatolij Gustschin" <agust@denx.de>,
	wahrenst@gmx.net, florian.fainelli@broadcom.com,
	u-boot@lists.denx.de, "Jan Čermák" <sairon@sairon.cz>
Subject: Re: [PATCH v4 0/6] rpi5: initial support
Date: Thu, 19 Sep 2024 16:01:44 +0200	[thread overview]
Message-ID: <1c9ebab90accb47abbd7ef2205c6b409@agner.ch> (raw)
In-Reply-To: <B1136352-B9D3-4990-B5E5-7C318809C957@suse.de>

Hi Ivan,

Thanks for the quick response!

On 2024-09-19 11:52, Ivan T. Ivanov wrote:
> Hi Stefan,
> 
>> On 19 Sep 2024, at 12:36, Stefan Agner <stefan@agner.ch> wrote:
>> 
>> Hi Ivan,
>> 
>> I am looking into enabling NVMe boot support using U-Boot on Raspberry
>> Pi 5. Which brings me to some questions wrt PCIe support (see below).
>> 
>> On 2024-01-10 13:29, Ivan T. Ivanov wrote:
>>> 
> 
> 
>>> * I am dropping PCIe patch for now. I made some progress on porting changes
>>>  from vendor Linux tree to U-Boot. Unfortunatly testing it is little bit
>>>  tricky. They are many devices behind PCIe, but more or less all of them
>>>  requires missing either "reset-controller" or "clock-controller" or
>>>  "pin-controller" drivers. I was able to probe "cdns,macb" device, but
>>>  access to ethernet PHY over MDIO bus is stucking. Then I ported
>>>  "raspberrypi,rp1-adc" driver from vendor Linux tree, but it requires
>>>  missing clock. And on top of that machine that I used for developing this
>>>  crashed and I lost my PCIe changes :-|. Anyway.
>> 
>> Have you tried using a M.2 HAT? This likely won't require much in terms
>> of enabling the device.
>> 
>> You write that you made some progress, is that compared to v3? Do you
>> mind sharing the latest version of your patches?
> 
> 
> No further progress on PCIe for U-Boot from my side was made, sorry.
> 

So v3 the patch you've shared in v3 is your latest state? I was
wondering since you wrote in this v4 patch set "I made some progress on
porting changes
 from vendor Linux tree to U-Boot."...


> Stan is working on adding support for 2712 PCIe in Linux [1]. Perhaps
> once this is complete we can work on adding U-Boot support for the same,
> unless someone don’t beat us, of course. 

Hm, it seems the link did not make it. I guess you meant to link this
patch set [1]

--
Stefan

[1]
https://lore.kernel.org/lkml/20240910151845.17308-1-svarbanov@suse.de/T/

> 
> Regards,
> Ivan

  reply	other threads:[~2024-09-19 14:01 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 12:29 [PATCH v4 0/6] rpi5: initial support Ivan T. Ivanov
2024-01-10 12:29 ` [PATCH v4 1/6] rpi5: add initial memory map for bcm2712 Ivan T. Ivanov
2024-01-10 17:57   ` Florian Fainelli
2024-01-10 12:29 ` [PATCH v4 2/6] rpi5: Use devicetree as alternative way to read IO base addresses Ivan T. Ivanov
2024-01-10 18:00   ` Florian Fainelli
2024-01-16  9:11     ` Ivan T. Ivanov
2024-01-10 12:29 ` [PATCH v4 3/6] rpi5: Use devicetree to retrieve board revision Ivan T. Ivanov
2024-01-10 12:29 ` [PATCH v4 4/6] bcm2835: Dynamically calculate bytes per pixel parameter Ivan T. Ivanov
2024-01-10 15:12   ` Matthias Brugger
2024-01-10 12:29 ` [PATCH v4 5/6] mmc: bcmstb: Add support for bcm2712 SD controller Ivan T. Ivanov
2024-01-11 22:07   ` Stefan Wahren
2024-01-12  7:44     ` Ivan T. Ivanov
2024-01-16  9:14       ` Ivan T. Ivanov
2024-01-10 12:29 ` [PATCH v4 6/6] configs: rpi_arm64: enable SDHCI BCMSTB driver Ivan T. Ivanov
2024-01-22 13:46 ` [PATCH v4 0/6] rpi5: initial support Matthias Brugger
2024-09-19  9:36 ` Stefan Agner
2024-09-19  9:52   ` Ivan T. Ivanov
2024-09-19 14:01     ` Stefan Agner [this message]
2024-09-19 14:22       ` Ivan T. Ivanov
  -- strict thread matches above, loose matches on Subject: below --
2024-01-12 13:10 Jens Maus
2024-01-17 15:07 ` Ivan T. Ivanov
2024-01-17 15:13   ` Jens Maus
2024-01-17 15:23     ` Ivan T. Ivanov
2024-01-17 15:30       ` Jens Maus
2024-01-17 16:45         ` Ivan T. Ivanov
2024-01-17 23:06           ` Jens Maus
2024-01-18  8:33             ` Ivan T. Ivanov
2024-01-18 17:18               ` Jens Maus
2024-01-19  5:29                 ` Ivan T. Ivanov
2024-01-19  7:21                   ` Jens Maus
2024-01-19  9:20                     ` Stefan Wahren
2024-01-19 10:49                       ` Jens Maus
     [not found]                         ` <sjmi6dftbgx56isfyjtaryehzq2iollwxm2etlspiygehh3n6v@k4ws56nsbgfn>
     [not found]                           ` <6C9E5E0C-9C27-45A4-886F-8B8C641EF7A3@jens-maus.de>
2024-01-19 13:46                             ` Ivan T. Ivanov
2024-01-19 13:54                               ` Jens Maus
2024-01-19 14:06                                 ` Ivan T. Ivanov
2024-01-19 14:08                                   ` Jens Maus
2024-01-19 14:24                                     ` Ivan T. Ivanov
2024-01-19 16:12                                       ` Jens Maus
2024-01-19 16:29                                         ` Ivan T. Ivanov
2024-01-19 16:53                                           ` Jens Maus
2024-01-19 21:26                                             ` Jens Maus
2024-01-20  9:22                                               ` Stefan Wahren
2024-01-20  9:48                                                 ` Jens Maus
2024-01-20 10:50                                                   ` Stefan Wahren
2024-01-22 11:57                                                     ` Ivan T. Ivanov
2024-01-22 14:16                                                       ` Ivan T. Ivanov
2024-01-22 14:30                                                         ` Mark Kettenis
2024-01-22 18:01                                                           ` Tom Rini
2024-01-23 11:11                                                         ` Jens Maus
2024-01-23 12:09                                                           ` Stefan Wahren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1c9ebab90accb47abbd7ef2205c6b409@agner.ch \
    --to=stefan@agner.ch \
    --cc=agust@denx.de \
    --cc=dmitry@bedrocksystems.com \
    --cc=fitzsim@fitzsim.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=iivanov@suse.de \
    --cc=jh80.chung@samsung.com \
    --cc=mbrugger@suse.com \
    --cc=pbrobinson@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=sairon@sairon.cz \
    --cc=u-boot@lists.denx.de \
    --cc=wahrenst@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox