mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-mediatek@lists.infradead.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Frank Wunderlich <linux@fw-web.de>
Subject: Re: Aw: Re: [RFC v3 00/11] Add BananaPi R3
Date: Sun, 13 Nov 2022 23:28:35 +0100	[thread overview]
Message-ID: <3a7cfa0a-970a-bc86-b519-7a7c925467b9@gmail.com> (raw)
In-Reply-To: <trinity-b1022e89-9e6b-417e-9506-431574251dc3-1668170275463@3c-app-gmx-bap63>



On 11/11/2022 13:37, Frank Wunderlich wrote:
> Hi
> 
>> Gesendet: Freitag, 11. November 2022 um 10:17 Uhr
>> Von: "Matthias Brugger" <matthias.bgg@gmail.com>
>> An: "Frank Wunderlich" <frank-w@public-files.de>, "Rob Herring" <robh+dt@kernel.org>
>> Cc: linux-mediatek@lists.infradead.org, "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, "Frank Wunderlich" <linux@fw-web.de>
>> Betreff: Re: Aw: [RFC v3 00/11] Add BananaPi R3
>>
>>
>>
>> On 10/11/2022 18:03, Frank Wunderlich wrote:
>>> Hi Rob,
>>>
>>> can you please take Patches 1+3 of v1 into your tree?
>>> due to reordering in my tree i missed them in this version
>>>
>>> https://patchwork.kernel.org/project/linux-mediatek/list/?series=685798
>>>
>>
>> They should go through the subsystem maintainers trees. I'd advise to resend,
>> dropping the RFC prefix and add the corresponding maintainers.
> 
> ok, wait for your push and i create v4 including the missing binding-patches and the reorder of wed-node together with my fixes.
> 
>> Regards,
>> Matthias
>>
>>> pcie-bindings are here:
>>>
>>> https://patchwork.kernel.org/project/linux-mediatek/list/?series=690172
>>>
>>> i found 1 error in bpi-r3 dts (properties from sfp1 not plural) which i will fix in next version and will drop
>>> the compile comment in dt overlays.
>>>
>>> also i've found this commit:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?h=dt/next&id=363547d2191cbc32ca954ba75d72908712398ff2
>>>
>>> so maybe i need to rename my overlay dts files to dtso?
>>>
>>> maybe the others can be applied (at least the mt7986 nodes)?
> 
> does this solve your question about dt-overlays?
> 
> just to note for all...it is all 1 board having sd+emmc on 1 mmc-controller and nand+nor on one spi. it depends on hardware-switches which devices are accessable (1mmc+1 spi). Adding dts for all possible combinations will add more dts (sd+nor, sd+nand, emmc+nor, emmc+nand) than adding the 2 overlays or adds redundant config.
> 

I wonder if in the end that wouldn't be part of U-Boot to pass the correct DTB 
depending on the HW switches. Just one idea I had is, to create on DTS with 
sd+nor+nand+emmc if that's possible. And then leave the permutations to the boot 
firmware (U-Boot).

Regards,
Matthias

> or should i copy the emmc/sd dts and adding once nor or nand? so we have the dtsi and dts for combinations above (=5 total)?
> 
>>> regards Frank
>>

      reply	other threads:[~2022-11-13 22:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  8:50 Frank Wunderlich
2022-11-06  8:50 ` [RFC v3 01/11] arm64: dts: mt7986: harmonize device node order Frank Wunderlich
2022-11-11  8:55   ` Matthias Brugger
2022-11-11  9:05     ` Matthias Brugger
2022-11-06  8:50 ` [RFC v3 02/11] arm64: dts: mt7986: add spi related device nodes Frank Wunderlich
2022-11-11  8:54   ` Matthias Brugger
2022-11-06  8:50 ` [RFC v3 03/11] arm64: dts: mt7986: add usb " Frank Wunderlich
2022-11-11  8:52   ` Matthias Brugger
2022-11-06  8:50 ` [RFC v3 04/11] arm64: dts: mt7986: add crypto " Frank Wunderlich
2022-11-11  8:56   ` Matthias Brugger
2022-11-06  8:50 ` [RFC v3 05/11] arm64: dts: mt7986: add mmc " Frank Wunderlich
2022-11-11  8:58   ` Matthias Brugger
2022-11-11 12:45     ` Aw: " Frank Wunderlich
2022-11-06  8:50 ` [RFC v3 06/11] arm64: dts: mt7986: add i2c node Frank Wunderlich
2022-11-11  9:06   ` Matthias Brugger
2022-11-06  8:50 ` [RFC v3 07/11] arm64: dts: mt7986: add pcie related device nodes Frank Wunderlich
2022-11-06  8:50 ` [RFC v3 08/11] dt-bindings: arm64: dts: mediatek: add compatible for bananapi r3 Frank Wunderlich
2022-11-06  8:50 ` [RFC v3 09/11] arm64: dts: mt7986: add Bananapi R3 Frank Wunderlich
2022-11-06  8:50 ` [RFC v3 10/11] arm64: dts: mt7986: add PCIe nodes to BananaPi-R3 Frank Wunderlich
2022-11-06  8:50 ` [RFC v3 11/11] arm64: dts: mt7986: add BPI-R3 nand/nor overlays Frank Wunderlich
2022-11-11  9:16   ` Matthias Brugger
2022-11-15 16:50     ` Aw: " Frank Wunderlich
2022-11-18 21:23     ` Rob Herring
2022-11-10 17:03 ` Aw: [RFC v3 00/11] Add BananaPi R3 Frank Wunderlich
2022-11-11  9:17   ` Matthias Brugger
2022-11-11 12:37     ` Aw: " Frank Wunderlich
2022-11-13 22:28       ` Matthias Brugger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3a7cfa0a-970a-bc86-b519-7a7c925467b9@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frank-w@public-files.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@fw-web.de \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®