Re: [PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

On Fri, Dec 7, 2018 at 7:52 PM Kishon Vijay Abraham I wrote: > > Hi, > > On 07/12/18 2:16 PM, Vivek Gautam wrote: > > On Fri, Dec 7, 2018 at 5:06 AM Evan Green wrote: > >> > >> Utilize the newly fixed up DT bindings to get the tx2 and rx2 register > >> regions for the second lane of dual-lane

Re: [PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

Hi, On 07/12/18 2:16 PM, Vivek Gautam wrote: > On Fri, Dec 7, 2018 at 5:06 AM Evan Green wrote: >> >> Utilize the newly fixed up DT bindings to get the tx2 and rx2 register >> regions for the second lane of dual-lane PHYs. Before this change, >> the driver was simply using lane one's register

Re: [PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

Hi, On 07/12/18 2:16 PM, Vivek Gautam wrote: > On Fri, Dec 7, 2018 at 5:06 AM Evan Green wrote: >> >> Utilize the newly fixed up DT bindings to get the tx2 and rx2 register >> regions for the second lane of dual-lane PHYs. Before this change, >> the driver was simply using lane one's register

Re: [PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

On Fri, Dec 7, 2018 at 5:06 AM Evan Green wrote: > > Utilize the newly fixed up DT bindings to get the tx2 and rx2 register > regions for the second lane of dual-lane PHYs. Before this change, > the driver was simply using lane one's register region and adding > 0x400, which reached well beyond

Re: [PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

On Fri, Dec 7, 2018 at 5:06 AM Evan Green wrote: > > Utilize the newly fixed up DT bindings to get the tx2 and rx2 register > regions for the second lane of dual-lane PHYs. Before this change, > the driver was simply using lane one's register region and adding > 0x400, which reached well beyond

[PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

Utilize the newly fixed up DT bindings to get the tx2 and rx2 register regions for the second lane of dual-lane PHYs. Before this change, the driver was simply using lane one's register region and adding 0x400, which reached well beyond the DT-specified register allocation. This would have been a

[PATCH v6 2/5] phy: qcom-qmp: Utilize fully-specified DT registers

Utilize the newly fixed up DT bindings to get the tx2 and rx2 register regions for the second lane of dual-lane PHYs. Before this change, the driver was simply using lane one's register region and adding 0x400, which reached well beyond the DT-specified register allocation. This would have been a