On 3/19/24 11:29, Krzysztof Kozlowski wrote:
On 17/03/2024 20:37, Ayush Singh wrote:
DONOTMERGE
Why? Explain then the purpose of this patch.
Well, it was suggested to have DONOTMERGE by Vaishnav in the patches
until dt bindings have been approved, since this patch touches different
subsystems. Here is the full context from v3:
The reasoning behind this is that these patches go in to separate maintainer trees and without the bindings merged first the device tree changes cannot be validated, thus it is a usual practice to get the bindings and driver merged first and the device tree changes to go in the next cycle. Another alternative is you can point to your fork with all the changes together.
this patch depends on patch 1
How? I don't see any dependency.
I think it is not allowed to have code in device tree unless a
corresponding dt-binding exists for the device. And thus every time the
dt-binding changes, this patch also needs to change.So I thought it is
dependent on patch 1.
Add mikroBUS connector support for Beagleplay.
Co-developed-by: Vaishnav M A <vaishnav@xxxxxxxxxxxxxxx>
Signed-off-by: Vaishnav M A <vaishnav@xxxxxxxxxxxxxxx>
Signed-off-by: Ayush Singh <ayushdevel1325@xxxxxxxxx>
---
.../arm64/boot/dts/ti/k3-am625-beagleplay.dts | 80 +++++++++++++++++--
1 file changed, 72 insertions(+), 8 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts b/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts
index a34e0df2ab86..e1dce1b80153 100644
--- a/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts
+++ b/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts
@@ -29,6 +29,7 @@ aliases {
i2c3 = &main_i2c3;
i2c4 = &wkup_i2c0;
i2c5 = &mcu_i2c0;
+ mikrobus0 = &mikrobus0;
mmc0 = &sdhci0;
mmc1 = &sdhci1;
mmc2 = &sdhci2;
@@ -230,6 +231,38 @@ simple-audio-card,codec {
};
};
Best regards,
Krzysztof
Link:
https://lore.kernel.org/lkml/CALudOK5v_uCUffxHGKS-jA-DKLNV7xwmKkxJwjHaMWWgDdPDqA@xxxxxxxxxxxxxx/
Patch v3
Ayush Singh
