Searched hist:"2 cae4a8586e253c00b3040152fd58b52168d89cd" (Results 1 – 3 of 3) sorted by relevance
| /rk3399_ARM-atf/drivers/marvell/mg_conf_cm3/ |
| H A D | mg_conf_cm3.h | 2cae4a8586e253c00b3040152fd58b52168d89cd Tue Jun 18 12:43:02 UTC 2019 Grzegorz Jaszczyk <jaz@semihalf.com> drivers: marvell: mg_conf_cm3: pass comphy lane number to AP FW
Since the AP process can be enabled on different setups, the information
about used comphy lane should be passed to AP FW. For instance:
- A8K development board uses comphy lane 2 for eth 0
- cn913x development board uses comphy lane 4 for eth 0
Change-Id: Icf001fb3eea4d9c24c09384e49844ecaf8655ad2
Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
|
| H A D | mg_conf_cm3.c | 2cae4a8586e253c00b3040152fd58b52168d89cd Tue Jun 18 12:43:02 UTC 2019 Grzegorz Jaszczyk <jaz@semihalf.com> drivers: marvell: mg_conf_cm3: pass comphy lane number to AP FW
Since the AP process can be enabled on different setups, the information
about used comphy lane should be passed to AP FW. For instance:
- A8K development board uses comphy lane 2 for eth 0
- cn913x development board uses comphy lane 4 for eth 0
Change-Id: Icf001fb3eea4d9c24c09384e49844ecaf8655ad2
Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
|
| /rk3399_ARM-atf/drivers/marvell/comphy/ |
| H A D | phy-comphy-cp110.c | 2cae4a8586e253c00b3040152fd58b52168d89cd Tue Jun 18 12:43:02 UTC 2019 Grzegorz Jaszczyk <jaz@semihalf.com> drivers: marvell: mg_conf_cm3: pass comphy lane number to AP FW
Since the AP process can be enabled on different setups, the information
about used comphy lane should be passed to AP FW. For instance:
- A8K development board uses comphy lane 2 for eth 0
- cn913x development board uses comphy lane 4 for eth 0
Change-Id: Icf001fb3eea4d9c24c09384e49844ecaf8655ad2
Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
|