mbox

[GIT,PULL] Allwinner fixes for 4.13 round 2

Message ID 20170818040447.ddz27hm3c2eashjr@wens.csie.org
State New
Headers show

Pull-request

https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git sunxi-fixes-for-4.13-2

Message

Chen-Yu Tsai Aug. 18, 2017, 4:04 a.m. UTC
Hi Arnd, Olof,

This is the second batch of fixes for 4.13. This is based on the first
batch of fixes that was already merged.

We still have some device tree binding changes for the H3 EMAC and
integrated Ethernet PHY we need to sort out for 4.13. If it is not
done by next week, I will send out revert patches for the driver,
device tree binding, and device tree changes. Or is this cutting
it too close and we should just revert them now?


Thanks
ChenYu

The following changes since commit c50f9fb6c535edf4731eecb53d91ebc297e82e5b:

  ARM: dts: sun8i: a83t: Switch to CCU device tree binding macros (2017-07-27 21:18:48 +0800)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git sunxi-fixes-for-4.13-2

for you to fetch changes up to d86e63e1f0b7868c55c8d4a54854b85e2bac690b:

  arm64: allwinner: h5: fix pinctrl IRQs (2017-08-14 14:18:21 +0800)

----------------------------------------------------------------
Allwinner fixes for 4.13, round 2

Three fixes adding a missing alias for the Ethernet controller on A64
boards. One adding a missing interrupt for the pin controller.

----------------------------------------------------------------
Icenowy Zheng (4):
      arm64: allwinner: a64: bananapi-m64: add missing ethernet0 alias
      arm64: allwinner: a64: pine64: add missing ethernet0 alias
      arm64: allwinner: a64: sopine: add missing ethernet0 alias
      arm64: allwinner: h5: fix pinctrl IRQs

 arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts     | 1 +
 arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts           | 1 +
 arch/arm64/boot/dts/allwinner/sun50i-a64-sopine-baseboard.dts | 1 +
 arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi                  | 3 +++
 4 files changed, 6 insertions(+)

Comments

Arnd Bergmann Aug. 18, 2017, 9:58 a.m. UTC | #1
On Fri, Aug 18, 2017 at 6:04 AM, Chen-Yu Tsai <wens@csie.org> wrote:
> Hi Arnd, Olof,
>
> This is the second batch of fixes for 4.13. This is based on the first
> batch of fixes that was already merged.

Pulled into fixes, thanks!

> We still have some device tree binding changes for the H3 EMAC and
> integrated Ethernet PHY we need to sort out for 4.13. If it is not
> done by next week, I will send out revert patches for the driver,
> device tree binding, and device tree changes. Or is this cutting
> it too close and we should just revert them now?

I need more information about the specific change to answer that.

Can you point me to the patches in question?

      Arnd
Chen-Yu Tsai Aug. 18, 2017, 10:12 a.m. UTC | #2
On Fri, Aug 18, 2017 at 5:58 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Fri, Aug 18, 2017 at 6:04 AM, Chen-Yu Tsai <wens@csie.org> wrote:
>> Hi Arnd, Olof,
>>
>> This is the second batch of fixes for 4.13. This is based on the first
>> batch of fixes that was already merged.
>
> Pulled into fixes, thanks!
>
>> We still have some device tree binding changes for the H3 EMAC and
>> integrated Ethernet PHY we need to sort out for 4.13. If it is not
>> done by next week, I will send out revert patches for the driver,
>> device tree binding, and device tree changes. Or is this cutting
>> it too close and we should just revert them now?
>
> I need more information about the specific change to answer that.

The hardware in question has an integrated PHY in the SoC, but can
also choose to use an external PHY. The changes would address two
issues: a) how to differentiate internal vs external PHY in the
device tree, and b) avoiding confusion when both are present and
assigned the same address (there is a mux in the hardware).

> Can you point me to the patches in question?

Here's v2 (which is not final):

    https://www.spinics.net/lists/arm-kernel/msg601325.html

Rob also chimed in on related patches:

    https://www.spinics.net/lists/arm-kernel/msg601482.html
    https://www.spinics.net/lists/devicetree/msg190976.html

ChenYu
Arnd Bergmann Aug. 18, 2017, 11:30 a.m. UTC | #3
On Fri, Aug 18, 2017 at 12:12 PM, Chen-Yu Tsai <wens@csie.org> wrote:
> On Fri, Aug 18, 2017 at 5:58 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Fri, Aug 18, 2017 at 6:04 AM, Chen-Yu Tsai <wens@csie.org> wrote:
>>> Hi Arnd, Olof,
>>>
>>> This is the second batch of fixes for 4.13. This is based on the first
>>> batch of fixes that was already merged.
>>
>> Pulled into fixes, thanks!
>>
>>> We still have some device tree binding changes for the H3 EMAC and
>>> integrated Ethernet PHY we need to sort out for 4.13. If it is not
>>> done by next week, I will send out revert patches for the driver,
>>> device tree binding, and device tree changes. Or is this cutting
>>> it too close and we should just revert them now?
>>
>> I need more information about the specific change to answer that.
>
> The hardware in question has an integrated PHY in the SoC, but can
> also choose to use an external PHY. The changes would address two
> issues: a) how to differentiate internal vs external PHY in the
> device tree, and b) avoiding confusion when both are present and
> assigned the same address (there is a mux in the hardware).
>
>> Can you point me to the patches in question?
>
> Here's v2 (which is not final):
>
>     https://www.spinics.net/lists/arm-kernel/msg601325.html
>
> Rob also chimed in on related patches:
>
>     https://www.spinics.net/lists/arm-kernel/msg601482.html
>     https://www.spinics.net/lists/devicetree/msg190976.html

Ok, it sounds like you are closing in on the final solution now,
If we get agreement on the fixes by next week, that should be
fine.

       Arnd