On 1/29/23 11:47, Patrick Wildt wrote:
On Sun, Jan 29, 2023 at 05:00:15AM +0100, Marek Vasut wrote:
On 1/29/23 04:28, Patrick Wildt wrote:
Am Sun, Jan 29, 2023 at 02:46:36AM +0100 schrieb Marek Vasut:
On 1/28/23 23:14, Patrick Wildt wrote:
The PCIe power domains are dependant on each other, w
On Sun, Jan 29, 2023 at 05:00:15AM +0100, Marek Vasut wrote:
> On 1/29/23 04:28, Patrick Wildt wrote:
> > Am Sun, Jan 29, 2023 at 02:46:36AM +0100 schrieb Marek Vasut:
> > > On 1/28/23 23:14, Patrick Wildt wrote:
> > > > The PCIe power domains are dependant on each other, which is why
> > > > the d
On 1/29/23 04:28, Patrick Wildt wrote:
Am Sun, Jan 29, 2023 at 02:46:36AM +0100 schrieb Marek Vasut:
On 1/28/23 23:14, Patrick Wildt wrote:
The PCIe power domains are dependant on each other, which is why
the device tree makes both PCIe controllers reference the PCIe1
power domain, which then d
Am Sun, Jan 29, 2023 at 02:46:36AM +0100 schrieb Marek Vasut:
> On 1/28/23 23:14, Patrick Wildt wrote:
> > The PCIe power domains are dependant on each other, which is why
> > the device tree makes both PCIe controllers reference the PCIe1
> > power domain, which then depends on the PCIe2 power dom
On 1/28/23 23:14, Patrick Wildt wrote:
The PCIe power domains are dependant on each other, which is why
the device tree makes both PCIe controllers reference the PCIe1
power domain, which then depends on the PCIe2 power domain.
Enabling the parent power domain used to be part of the driver,
but
The PCIe power domains are dependant on each other, which is why
the device tree makes both PCIe controllers reference the PCIe1
power domain, which then depends on the PCIe2 power domain.
Enabling the parent power domain used to be part of the driver,
but got partially lost in the rewrite. Add t
6 matches
Mail list logo
