mbox series

[GIT,PULL] arm64: dts: updates for v5.17

Message ID 0d05e8b6-c56f-bad7-00c1-44682cedb38f@suse.com (mailing list archive)
State New, archived
Headers show
Series [GIT,PULL] arm64: dts: updates for v5.17 | expand

Pull-request

https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/ tags/v5.16-next-dts64

Message

Matthias Brugger Dec. 18, 2021, 8:42 a.m. UTC
Hi Arnd and Olof,

Please take a look on the below patches for aarch64 based MediaTek boards.
In this round we add support for the mt8183 based Acer Crhomebook 314, as well 
as we add support to several SKUs for mt8183 based Chromebooks.
Apart from that we add basic support to the mt7986 in both variants (mt7986a, 
mt7986b). The difference between the both SoCs are the pin-controller capabilities.

Hope you are fine with this pull request.

Regards,
Matthias

---

The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:

   Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)

are available in the Git repository at:

   https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/ 
tags/v5.16-next-dts64

for you to fetch changes up to f40c0f800f15e9e3566cb39a9eee2855c634eb5f:

   arm64: dts: mediatek: add pinctrl support for mt7986b (2021-12-15 21:06:35 +0100)

----------------------------------------------------------------
mt8183:
- add Acer Chromebook 314
- evb: add node to read thermisor from AUXIN0
- add several sku's for Lenovo IdeaPad Flex 3 Chromebook and ASUS Chromebook 
Detachable CM3
- update sensor mapping of the board temperature sensor
- add some coresight nodes for CPU debugging
- USB Type C connector description to all Chromebooks

mt8192, mt8516:
- smaller i2c related fixes

mt8173:
- enable backlight enable pin to all Chromebooks

mt7986[a,b]:
- add basic support

----------------------------------------------------------------
AngeloGioacchino Del Regno (3):
       arm64: dts: mediatek: mt8173: Add gce-client-reg to display od/ufo
       arm64: dts: mediatek: mt8173-elm: Move pwm pinctrl to pwm0 node
       arm64: dts: mediatek: mt8173-elm: Add backlight enable pin config

Ben Tseng (1):
       arm64: dts: mt8183-kukui: Update Tboard sensor mapping table

Fabien Parent (3):
       arm64: dts: mediatek: mt8192: fix i2c node names
       arm64: dts: mediatek: mt8516: remove 2 invalid i2c clocks
       arm64: dts: mediatek: mt8183-evb: Add node for thermistor

Hsin-Yi Wang (7):
       arm64: dts: mt8183: jacuzzi: remove unused ddc-i2c-bus
       arm64: dts: mt8183: Add kukui-jacuzzi-cozmo board
       arm64: dts: mt8183: Add more fennel SKUs
       arm64: dts: mt8183: Add kakadu sku22
       dt-bindings: arm64: dts: mediatek: Add mt8183-kukui-jacuzzi-cozmo
       dt-bindings: arm64: dts: mediatek: Add more SKUs for mt8183 fennel board
       dt-bindings: arm64: dts: mediatek: Add sku22 for mt8183 kakadu board

Prashant Malani (1):
       arm64: dts: mt8183: kukui: Add Type C node

Sam Shih (4):
       dt-bindings: arm64: dts: mediatek: Add mt7986 series
       arm64: dts: mediatek: add basic mt7986 support
       arm64: dts: mediatek: add pinctrl support for mt7986a
       arm64: dts: mediatek: add pinctrl support for mt7986b

Seiya Wang (1):
       arm64: dts: mt8183: support coresight-cpu-debug for mt8183

Tinghan Shen (1):
       arm64: dts: mt8183: change rpmsg property name

  .../devicetree/bindings/arm/mediatek.yaml          |  20 +++
  arch/arm64/boot/dts/mediatek/Makefile              |   6 +
  arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts       |  57 +++++++
  arch/arm64/boot/dts/mediatek/mt7986a.dtsi          | 169 +++++++++++++++++++++
  arch/arm64/boot/dts/mediatek/mt7986b-rfb.dts       |  29 ++++
  arch/arm64/boot/dts/mediatek/mt7986b.dtsi          |  12 ++
  arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi       |  10 +-
  arch/arm64/boot/dts/mediatek/mt8173.dtsi           |   2 +
  arch/arm64/boot/dts/mediatek/mt8183-evb.dts        |   8 +
  .../dts/mediatek/mt8183-kukui-jacuzzi-cozmo.dts    |  36 +++++
  .../mediatek/mt8183-kukui-jacuzzi-fennel-sku1.dts  |   1 +
  .../mediatek/mt8183-kukui-jacuzzi-fennel-sku6.dts  |   1 +
  .../mediatek/mt8183-kukui-jacuzzi-fennel-sku7.dts  |  33 ++++
  .../dts/mediatek/mt8183-kukui-jacuzzi-fennel.dtsi  |   1 -
  .../mt8183-kukui-jacuzzi-fennel14-sku2.dts         |  17 +++
  .../dts/mediatek/mt8183-kukui-jacuzzi-fennel14.dts |   1 +
  .../boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi    |   1 -
  .../dts/mediatek/mt8183-kukui-kakadu-sku22.dts     |  19 +++
  arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi     | 124 ++++++++-------
  arch/arm64/boot/dts/mediatek/mt8183.dtsi           |  64 ++++++++
  arch/arm64/boot/dts/mediatek/mt8192.dtsi           |  20 +--
  arch/arm64/boot/dts/mediatek/mt8516.dtsi           |  27 +---
  22 files changed, 569 insertions(+), 89 deletions(-)
  create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts
  create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a.dtsi
  create mode 100644 arch/arm64/boot/dts/mediatek/mt7986b-rfb.dts
  create mode 100644 arch/arm64/boot/dts/mediatek/mt7986b.dtsi
  create mode 100644 arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-cozmo.dts
  create mode 100644 
arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-fennel-sku7.dts
  create mode 100644 
arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-fennel14-sku2.dts
  create mode 100644 arch/arm64/boot/dts/mediatek/mt8183-kukui-kakadu-sku22.dts

Comments

Arnd Bergmann Dec. 20, 2021, 4:18 p.m. UTC | #1
On Sat, Dec 18, 2021 at 9:42 AM Matthias Brugger <mbrugger@suse.com> wrote:
>
> Hi Arnd and Olof,
>
> Please take a look on the below patches for aarch64 based MediaTek boards.
> In this round we add support for the mt8183 based Acer Crhomebook 314, as well
> as we add support to several SKUs for mt8183 based Chromebooks.
> Apart from that we add basic support to the mt7986 in both variants (mt7986a,
> mt7986b). The difference between the both SoCs are the pin-controller capabilities.
>
> Hope you are fine with this pull request.

I've pulled both tags, but I have two minor comments:

- please put "mediatek" into the subject, that helps when looking at
the pull requests
  with pwclient, which does not show the author by default

- I was expecting you to send a branch for the new EN7523 SoC as well. Did that
  end up not making it in time?

       Arnd
Matthias Brugger Dec. 29, 2021, 3:29 p.m. UTC | #2
Hi Arnd,

On 20/12/2021 17:18, Arnd Bergmann wrote:
> On Sat, Dec 18, 2021 at 9:42 AM Matthias Brugger <mbrugger@suse.com> wrote:
>>
>> Hi Arnd and Olof,
>>
>> Please take a look on the below patches for aarch64 based MediaTek boards.
>> In this round we add support for the mt8183 based Acer Crhomebook 314, as well
>> as we add support to several SKUs for mt8183 based Chromebooks.
>> Apart from that we add basic support to the mt7986 in both variants (mt7986a,
>> mt7986b). The difference between the both SoCs are the pin-controller capabilities.
>>
>> Hope you are fine with this pull request.
> 
> I've pulled both tags, but I have two minor comments:
> 
> - please put "mediatek" into the subject, that helps when looking at
> the pull requests
>    with pwclient, which does not show the author by default
> 

I did this pull request with a lot of time pressure and forgot about it. My 
apologies, I'll try to not forget next time.

> - I was expecting you to send a branch for the new EN7523 SoC as well. Did that
>    end up not making it in time?
> 

As I have seen, in the meantime you reviewed some parts yourself. I took the 
first two patches in my tree, but we should coordinate for the rest. If  you 
want to take it through the SOC tree or if I should take it through the mediatek 
tree. As Airoha is a subsidiary of MediaTek, I suppose in the long run, you want 
it do be part of the Mediatek tree, correct?

Regards,
Matthias
Arnd Bergmann Dec. 30, 2021, 1:40 a.m. UTC | #3
On Wed, Dec 29, 2021 at 10:29 AM Matthias Brugger
<matthias.bgg@gmail.com> wrote:
> On 20/12/2021 17:18, Arnd Bergmann wrote:
> > On Sat, Dec 18, 2021 at 9:42 AM Matthias Brugger <mbrugger@suse.com> wrote:
> >>
> >> Please take a look on the below patches for aarch64 based MediaTek boards.
> >> In this round we add support for the mt8183 based Acer Crhomebook 314, as well
> >> as we add support to several SKUs for mt8183 based Chromebooks.
> >> Apart from that we add basic support to the mt7986 in both variants (mt7986a,
> >> mt7986b). The difference between the both SoCs are the pin-controller capabilities.
> >>
> >> Hope you are fine with this pull request.
> >
> > I've pulled both tags, but I have two minor comments:
> >
> > - please put "mediatek" into the subject, that helps when looking at
> > the pull requests
> >    with pwclient, which does not show the author by default
> >
>
> I did this pull request with a lot of time pressure and forgot about it. My
> apologies, I'll try to not forget next time.
>
> > - I was expecting you to send a branch for the new EN7523 SoC as well. Did that
> >    end up not making it in time?
> >
>
> As I have seen, in the meantime you reviewed some parts yourself. I took the
> first two patches in my tree, but we should coordinate for the rest. If  you
> want to take it through the SOC tree or if I should take it through the mediatek
> tree. As Airoha is a subsidiary of MediaTek, I suppose in the long run, you want
> it do be part of the Mediatek tree, correct?

I talked to Felix about it last week, I think it would be best if you handle the
arch/{arm,arm64}/ bits for Airoha as part of the mach-mediatek and merge
changes the same way as the mt76xx, mt69xx and mt81xx series. For the
initial submission, of en7623, having a single branch that contains both
the arch/* and drivers/* with the appropriate Acks would make the most
sense, to avoid spreading it out over multiple merge windows, though it's
not too late for 5.17.

         Arnd
Matthias Brugger Dec. 30, 2021, 12:26 p.m. UTC | #4
On 30/12/2021 02:40, Arnd Bergmann wrote:
> On Wed, Dec 29, 2021 at 10:29 AM Matthias Brugger
> <matthias.bgg@gmail.com> wrote:
>> On 20/12/2021 17:18, Arnd Bergmann wrote:
>>> On Sat, Dec 18, 2021 at 9:42 AM Matthias Brugger <mbrugger@suse.com> wrote:
>>>>
>>>> Please take a look on the below patches for aarch64 based MediaTek boards.
>>>> In this round we add support for the mt8183 based Acer Crhomebook 314, as well
>>>> as we add support to several SKUs for mt8183 based Chromebooks.
>>>> Apart from that we add basic support to the mt7986 in both variants (mt7986a,
>>>> mt7986b). The difference between the both SoCs are the pin-controller capabilities.
>>>>
>>>> Hope you are fine with this pull request.
>>>
>>> I've pulled both tags, but I have two minor comments:
>>>
>>> - please put "mediatek" into the subject, that helps when looking at
>>> the pull requests
>>>     with pwclient, which does not show the author by default
>>>
>>
>> I did this pull request with a lot of time pressure and forgot about it. My
>> apologies, I'll try to not forget next time.
>>
>>> - I was expecting you to send a branch for the new EN7523 SoC as well. Did that
>>>     end up not making it in time?
>>>
>>
>> As I have seen, in the meantime you reviewed some parts yourself. I took the
>> first two patches in my tree, but we should coordinate for the rest. If  you
>> want to take it through the SOC tree or if I should take it through the mediatek
>> tree. As Airoha is a subsidiary of MediaTek, I suppose in the long run, you want
>> it do be part of the Mediatek tree, correct?
> 
> I talked to Felix about it last week, I think it would be best if you handle the
> arch/{arm,arm64}/ bits for Airoha as part of the mach-mediatek and merge
> changes the same way as the mt76xx, mt69xx and mt81xx series. For the
> initial submission, of en7623, having a single branch that contains both
> the arch/* and drivers/* with the appropriate Acks would make the most
> sense, to avoid spreading it out over multiple merge windows, though it's
> not too late for 5.17.
> 

Sounds good. Although it's still not clear to me, if you want to take the 
initial submission or if I should take that.

And I understand that it's a typo and we are too late for 5.17 given that we are 
in v5.16-rc7 already. Anyway I had some comments on the arm bits and we are 
still lacking the Acked-by for the clock driver.

Regards,
Matthias