Hi Lukasz,
On Fri, 25 Apr 2025 at 16:32, Lukasz Czechowski
wrote:
>
> Currently the check in usb_onboard_hub_bind is relying on specific
> compatible string for the Michrochip USB5744. Replace this with
> more generic approach that will allow to add new types of devices
> to the of_match table. B
Hi Quentin,
On Mon, 19 May 2025 at 18:45, Quentin Schulz wrote:
>
> Hi Anand,
>
> On 5/19/25 2:42 PM, Anand Moon wrote:
> > Hi Lukasz,
> >
> > On Fri, 25 Apr 2025 at 16:32, Lukasz Czechowski
> > wrote:
> >>
> >> Currently the check in usb_onboard_hub_bind is relying on specific
> >> compatible s
Hi Anand,
On 5/19/25 2:42 PM, Anand Moon wrote:
Hi Lukasz,
On Fri, 25 Apr 2025 at 16:32, Lukasz Czechowski
wrote:
Currently the check in usb_onboard_hub_bind is relying on specific
compatible string for the Michrochip USB5744. Replace this with
more generic approach that will allow to add ne
Hi Quentin,
pt., 16 maj 2025 o 16:28 Quentin Schulz napisał(a):
>
> Hi Lukasz,
>
> On 4/25/25 12:56 PM, Lukasz Czechowski wrote:
> > Currently the check in usb_onboard_hub_bind is relying on specific
> > compatible string for the Michrochip USB5744. Replace this with
> > more generic approach tha
Hi Lukasz,
On 4/25/25 12:56 PM, Lukasz Czechowski wrote:
Currently the check in usb_onboard_hub_bind is relying on specific
compatible string for the Michrochip USB5744. Replace this with
more generic approach that will allow to add new types of devices
to the of_match table. Because the driver
Currently the check in usb_onboard_hub_bind is relying on specific
compatible string for the Michrochip USB5744. Replace this with
more generic approach that will allow to add new types of devices
to the of_match table. Because the driver only needs to bind one
"half" of the hub, the peer-hub node
6 matches
Mail list logo