public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Anand Moon" <linux.amoon@gmail.com>,
	"Niklas Cassel" <cassel@kernel.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: dw-rockchip: Enable async probe by default
Date: Wed, 15 Jan 2025 23:19:48 +0530	[thread overview]
Message-ID: <20250115174948.yippqwr5mekb6o4d@thinkpad> (raw)
In-Reply-To: <c08f3d69-1f3d-49a6-96ac-0c2f990f9a8d@lunn.ch>

On Tue, Jan 07, 2025 at 02:13:34PM +0100, Andrew Lunn wrote:
> > I was just trying to understand the call trace for mdio bus which got
> > me confused.
> > 
> > [0] https://lore.kernel.org/all/Z3fKkTSFFcU9gQLg@ryzen/
> 
> There is nothing particularly unusual in there. We see PCI bus
> enumeration has found a device and bound a driver to it. The driver
> has instantiated an MDIO bus, which has scanned the MDIO bus and found
> a PHY. The phylib core then tried to load the kernel module needed to
> drive the PHY.
> 
> Just because it is a PCI device does not mean firmware has to control
> all the hardware. Linux has no problems controlling all this, and it
> saves reinventing the wheel in firmware, avoids firmware bugs, and
> allows new features to be added etc.
> 

Most of the time, it would be hard to define the properties of the PCI device's
internal bus in devicetree. For instance, the pinctrl/clock properties which
linux expects are to be connected to the host SoC, and not to the PCI device's
SoC (unless the whole device's SoC is defined).

Not saying that it is not possible but all, but very rare.

- Mani

-- 
மணிவண்ணன் சதாசிவம்


  parent reply	other threads:[~2025-01-15 17:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  7:36 [PATCH v2] PCI: dw-rockchip: Enable async probe by default Anand Moon
2025-01-03 11:31 ` Niklas Cassel
2025-01-03 13:54   ` Anand Moon
2025-01-03 14:25     ` Niklas Cassel
2025-01-03 14:40       ` Anand Moon
2025-01-03 14:45         ` Niklas Cassel
2025-01-03 15:06           ` Anand Moon
2025-01-03 15:10             ` Niklas Cassel
2025-01-03 15:29               ` Anand Moon
2025-01-03 15:45                 ` Niklas Cassel
2025-01-05 16:35                 ` Manivannan Sadhasivam
2025-01-05 17:46       ` Anand Moon
2025-01-03 16:04     ` Andrew Lunn
2025-01-05 17:46       ` Anand Moon
2025-01-05 17:57         ` Andrew Lunn
2025-01-06  7:58           ` Anand Moon
2025-01-06 12:02             ` Niklas Cassel
2025-01-06 13:44               ` Andrew Lunn
2025-01-07 11:13                 ` Anand Moon
2025-01-07 13:13                   ` Andrew Lunn
2025-01-07 14:57                     ` Anand Moon
2025-01-15 17:49                     ` Manivannan Sadhasivam [this message]
2026-01-29 14:06 ` Grimmauld
2026-01-30 10:25   ` Niklas Cassel
2026-01-31  9:38     ` Anand Moon
2026-02-02  9:54       ` Niklas Cassel
2026-02-02 18:05         ` Anand Moon
2026-02-03 11:01           ` Niklas Cassel
2026-02-02 10:02     ` Niklas Cassel
2026-02-02 18:07       ` Anand Moon

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=20250115174948.yippqwr5mekb6o4d@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=andrew@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=heiko@sntech.de \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux.amoon@gmail.com \
    --cc=lpieralisi@kernel.org \
    --cc=robh@kernel.org \
    /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