* Re: (subset) [PATCH 1/2] arm64: dts: ti: k3-am62p5-sk: minor whitespace cleanup
From: Nishanth Menon @ 2024-04-09 19:36 UTC (permalink / raw)
To: Benoît Cousson, Tony Lindgren, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Vignesh Raghavendra,
Tero Kristo, linux-omap, devicetree, linux-kernel,
linux-arm-kernel, Krzysztof Kozlowski
Cc: Nishanth Menon
In-Reply-To: <20240208105146.128645-1-krzysztof.kozlowski@linaro.org>
Hi Krzysztof Kozlowski,
On Thu, 08 Feb 2024 11:51:45 +0100, Krzysztof Kozlowski wrote:
> The DTS code coding style expects exactly one space before '{'
> character.
>
>
As discussed offline, I am picking this patch up.
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-am62p5-sk: minor whitespace cleanup
commit: 45ab8daed512258c07fd14536a3633440dabfe84
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH] arm64: dts: ti: verdin-am62: Set memory size to 2gb
From: Nishanth Menon @ 2024-04-09 19:37 UTC (permalink / raw)
To: max.krummenacher, max.oss.09
Cc: Nishanth Menon, conor+dt, devicetree, francesco.dolcini, kristo,
krzysztof.kozlowski+dt, linux-arm-kernel, linux-kernel, robh+dt,
vigneshr, stable
In-Reply-To: <20240320142937.2028707-1-max.oss.09@gmail.com>
Hi max.oss.09@gmail.com,
On Wed, 20 Mar 2024 15:29:37 +0100, max.oss.09@gmail.com wrote:
> The maximum DDR RAM size stuffed on the Verdin AM62 is 2GB,
> correct the memory node accordingly.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: verdin-am62: Set memory size to 2gb
commit: 7e8eddc5291f5c94dd28227a73b7573b671f4a05
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH v2] arm64: dts: ti: verdin-am62: use SD1 CD as GPIO
From: Nishanth Menon @ 2024-04-09 19:37 UTC (permalink / raw)
To: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Francesco Dolcini
Cc: Nishanth Menon, Francesco Dolcini, linux-arm-kernel, devicetree,
linux-kernel, João Paulo Silva Gonçalves
In-Reply-To: <20240325083340.89568-1-francesco@dolcini.it>
Hi Francesco Dolcini,
On Mon, 25 Mar 2024 09:33:40 +0100, Francesco Dolcini wrote:
> TI SDHCI instance has a hardware debounce timer of 1 second as described
> in commit 7ca0f166f5b2 ("mmc: sdhci_am654: Add workaround for card detect
> debounce timer"), because of this the boot time increases of up to 1
> second.
>
> Workaround the issue the same way that is done on
> arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts, using the SD1 CD as
> GPIO.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: verdin-am62: use SD1 CD as GPIO
commit: 08efdb8c41db2ea7a13e6a7e15bc167c1d96c456
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH V2] arm64: dts: ti: k3-am625-beagleplay: Use mmc-pwrseq for wl18xx enable
From: Nishanth Menon @ 2024-04-09 19:38 UTC (permalink / raw)
To: Tero Kristo, Vignesh Raghavendra, Nishanth Menon
Cc: Robert Nelson, Conor Dooley, Krzysztof Kozlowski, Rob Herring,
linux-kernel, devicetree, linux-arm-kernel, Shengyu Qu,
Sukrut Bellary, Javier Martinez Canillas, Bill Mills
In-Reply-To: <20240325143511.2144768-1-nm@ti.com>
Hi Nishanth Menon,
On Mon, 25 Mar 2024 09:35:10 -0500, Nishanth Menon wrote:
> BeaglePlay SBC[1] has Texas Instrument's WL18xx WiFi chipset[2].
>
> Currently, WLAN_EN is configured as regulator and regulator-always-on.
> However, the timing and wlan_en sequencing is not correctly modelled.
>
> This causes the sdio access to fail during runtime-pm power operations
> saving or during system suspend/resume/hibernation/freeze operations.
> This is because the WLAN_EN line is not deasserted to low '0' to power
> down the WiFi. So during restore, the WiFi driver tries to load the FW
> without following correct power sequence. WLAN_EN => '1'/assert (high)
> to power-up the chipset.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am625-beagleplay: Use mmc-pwrseq for wl18xx enable
commit: 31d5c43719bbd147d7e2c53ad2ef17953c68f458
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH] arm64: dts: ti: k3-am62-lp-sk: Remove tps65219 power-button
From: Nishanth Menon @ 2024-04-09 19:38 UTC (permalink / raw)
To: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Anand Gadiyar,
Markus Schneider-Pargmann
Cc: Nishanth Menon, linux-arm-kernel, devicetree, linux-kernel
In-Reply-To: <20240325152029.2933445-1-msp@baylibre.com>
Hi Markus Schneider-Pargmann,
On Mon, 25 Mar 2024 16:20:29 +0100, Markus Schneider-Pargmann wrote:
> On am62-lp-sk the PMIC is not wired up to a power button. Remove this
> property. This fixes issues observed when entering a very deep sleep
> state that is not yet available upstream.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am62-lp-sk: Remove tps65219 power-button
commit: 20b7a6af07b80771043d3beddd80720a40dce60c
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH 1/6] arm64: dts: ti: k3-am65: Remove UART baud rate selection
From: Nishanth Menon @ 2024-04-09 19:39 UTC (permalink / raw)
To: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Andrew Davis
Cc: Nishanth Menon, linux-arm-kernel, devicetree, linux-kernel
In-Reply-To: <20240326185441.29656-1-afd@ti.com>
Hi Andrew Davis,
On Tue, 26 Mar 2024 13:54:36 -0500, Andrew Davis wrote:
> As described in the binding document for the "current-speed" property:
>
> "This should only be present in case a driver has no chance to know the
> baud rate of the slave device."
>
> This is not the case for the UART used in K3 devices, the current
> baud-rate can be calculated from the registers. Having this property
> has the effect of actually skipping the baud-rate setup in some drivers
> as it assumes it will already be set to this rate, which may not always
> be the case.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/6] arm64: dts: ti: k3-am65: Remove UART baud rate selection
commit: 9a1cedcdb98387bfc5d4fb9f1a1ada9121d32757
[2/6] arm64: dts: ti: k3-am64: Remove UART baud rate selection
commit: 78331a044106f7022915058376ac56ec5d048124
[3/6] arm64: dts: ti: k3-j7200: Remove UART baud rate selection
commit: 69dfa876d4b03f7bc043b196c472fca5d339722a
[4/6] arm64: dts: ti: k3-j721e: Remove UART baud rate selection
commit: 14e556b08380b20833c5e2f6a5826d0669e0e0fa
[5/6] arm64: dts: ti: k3-j721s2: Remove UART baud rate selection
commit: cfcfcd47c9f049be4ebcee90eafaf78b03cdf05f
[6/6] arm64: dts: ti: k3-j784s4: Remove UART baud rate selection
commit: bd305a20fd338690fdd8ab8c4a50ab9d14066dfe
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH v1 0/2] arm64: dts: ti: k3-am625-verdin: fix GPIOs pinctrl
From: Nishanth Menon @ 2024-04-09 19:39 UTC (permalink / raw)
To: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Francesco Dolcini
Cc: Nishanth Menon, Francesco Dolcini, linux-arm-kernel, devicetree,
linux-kernel
In-Reply-To: <20240327182801.5997-1-francesco@dolcini.it>
Hi Francesco Dolcini,
On Wed, 27 Mar 2024 19:27:59 +0100, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> Fix a couple of issues on the Verdin AM62 pinctrl affecting multiple
> carrier boards.
>
> The first patch fixes a mistake on the pinctrl of the verdin-am62 mallow
> carrier board.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: verdin-am62: mallow: fix GPIOs pinctrl
commit: 8760892b8a3e20fdd996e59daf0a5f847b238967
[2/2] arm64: dts: ti: k3-am625-verdin: add PCIe reset gpio hog
commit: d3c702186abe01e24f962627ec67fcad8106c79d
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH 1/2] dt-bindings: arm: ti: Add BeagleY-AI
From: Nishanth Menon @ 2024-04-09 19:41 UTC (permalink / raw)
To: linux-arm-kernel, linux-kernel, devicetree, Robert Nelson
Cc: Nishanth Menon, Rob Herring, Jared McArthur, Jason Kridner,
Deepak Khatri
In-Reply-To: <20240328191205.82295-1-robertcnelson@gmail.com>
Hi Robert Nelson,
On Thu, 28 Mar 2024 14:12:04 -0500, Robert Nelson wrote:
> This board is based on ti,j722s
>
> https://beagley-ai.org/
> https://openbeagle.org/beagley-ai/beagley-ai
>
>
Robert,
I did a couple of sync as part of rebase - but for the future, please
be aware of [2]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] dt-bindings: arm: ti: Add BeagleY-AI
commit: d2b3e3b544d7e657406db3bdcdc296f02f4f07c9
[2/2] arm64: dts: ti: Add k3-j722s-beagley-ai
commit: f6a61274cc851e1dbae82b5fa2d3e7087dccf85b
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
[2] https://docs.kernel.org/devicetree/bindings/dts-coding-style.html#order-of-properties-in-device-node
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH 0/2] Increase CAN max bitrate for phyCORE-AM62x and phyCORE-am64x
From: Nishanth Menon @ 2024-04-09 19:41 UTC (permalink / raw)
To: vigneshr, kristo, robh, krzysztof.kozlowski+dt, conor+dt,
Nathan Morrisson
Cc: Nishanth Menon, linux-arm-kernel, devicetree, linux-kernel,
upstream, w.egorov
In-Reply-To: <20240402160825.1516036-1-nmorrisson@phytec.com>
Hi Nathan Morrisson,
On Tue, 02 Apr 2024 09:08:23 -0700, Nathan Morrisson wrote:
> Nathan Morrisson (2):
> arm64: dts: ti: k3-am625-phyboard-lyra-rdk: Increase CAN max bitrate
> arm64: dts: ti: k3-am642-phyboard-electra-rdk: Increase CAN max
> bitrate
>
> arch/arm64/boot/dts/ti/k3-am625-phyboard-lyra-rdk.dts | 2 +-
> arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-am625-phyboard-lyra-rdk: Increase CAN max bitrate
commit: 3de136cd0d601e6051aae86903e0e83077a436c3
[2/2] arm64: dts: ti: k3-am642-phyboard-electra-rdk: Increase CAN max bitrate
commit: f360d7f8bb7b115103017f406aa90605781fb05c
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH v2] arm64: dts: ti: k3-{am62p,j722s}: Disable ethernet by default
From: Nishanth Menon @ 2024-04-09 19:42 UTC (permalink / raw)
To: Francesco Dolcini, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Michael Walle
Cc: Nishanth Menon, linux-arm-kernel, devicetree, linux-kernel
In-Reply-To: <20240403101545.3932437-1-mwalle@kernel.org>
Hi Michael Walle,
On Wed, 03 Apr 2024 12:15:45 +0200, Michael Walle wrote:
> Device tree best practice is to disable any external interface in the
> dtsi and just enable them if needed in the device tree. Thus, disable
> the ethernet switch and its ports by default and just enable the ones
> used by the EVMs in their device trees.
>
> There is no functional change.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-{am62p,j722s}: Disable ethernet by default
commit: f3d27e84814641192570fbe7a1cfdbb741a250e8
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH v2] arm64: dts: ti: k3-j722s-evm: Enable eMMC support
From: Nishanth Menon @ 2024-04-09 19:43 UTC (permalink / raw)
To: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Michael Walle
Cc: Nishanth Menon, linux-arm-kernel, devicetree, linux-kernel
In-Reply-To: <20240403102302.3934932-1-mwalle@kernel.org>
Hi Michael Walle,
On Wed, 03 Apr 2024 12:23:02 +0200, Michael Walle wrote:
> The J722S EVM has an on-board eMMC. Enable the SDHC interface for it.
> There is no pinmuxing required because the interface has dedicated pins.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-j722s-evm: Enable eMMC support
commit: ab833a6478e5376f8076be41109d74387ab8460e
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH 0/4] Unconditionally register TI-SCI reset handler
From: Nishanth Menon @ 2024-04-09 19:53 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Santosh Shilimkar,
Vignesh Raghavendra, Andrew Davis
Cc: Nishanth Menon, devicetree, linux-arm-kernel, linux-kernel
In-Reply-To: <20240326223730.54639-1-afd@ti.com>
Hi Andrew Davis,
On Tue, 26 Mar 2024 17:37:26 -0500, Andrew Davis wrote:
> This series is the replacement for this series[0] and is based on a
> comment in that series by Rob here[1].
>
> First patch is just a fixup, second patch is the core of the series.
>
> Thanks,
> Andrew
>
> [...]
I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!
[1/4] firmware: ti_sci: Use devm_register_restart_handler()
commit: c0e5a431442d7bbfbd3704212680e49faa8ee46c
[2/4] firmware: ti_sci: Unconditionally register reset handler
commit: 8c8ff39838e02b6df91b80e086426dcb9ac86908
and the following to branch ti-keystone-dts-next on [1].
[3/4] ARM: dts: ti: keystone: k2g: Remove ti,system-reboot-controller property
commit: 345d22f4f45369a33b416a96c92bc273e41d695b
[4/4] dt-bindings: arm: keystone: Remove ti,system-reboot-controller property
commit: 60242b20fe784ef9142050be8b68bd85e94be557
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply
* Re: [PATCH v3 1/2] dt-bindings: dma: fsl-edma: remove 'clocks' from required
From: Krzysztof Kozlowski @ 2024-04-09 20:02 UTC (permalink / raw)
To: Frank Li
Cc: conor+dt, devicetree, dmaengine, imx, krzysztof.kozlowski+dt,
linux-kernel, peng.fan, robh, vkoul
In-Reply-To: <20240409185416.2224609-1-Frank.Li@nxp.com>
On 09/04/2024 20:54, Frank Li wrote:
> fsl,imx8qm-adma and fsl,imx8qm-edma don't require 'clocks'. Remove it from
> required and add 'if' block for other compatible string to keep the same
> restrictions.
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
>
> Notes:
> Change from v2 to v3
> - rebase to dmaengine/next
This fails...
>
> diff --git a/Documentation/devicetree/bindings/dma/fsl,edma.yaml b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> index 825f4715499e5..657a7d3ebf857 100644
> --- a/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> +++ b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> @@ -82,7 +82,6 @@ required:
> - compatible
> - reg
> - interrupts
> - - clocks
> - dma-channels
>
> allOf:
> @@ -187,6 +186,22 @@ allOf:
> "#dma-cells":
> const: 3
>
> + - if:
> + properties:
> + compatible:
> + contains:
It does not look like you tested the bindings, at least after quick
look. Please run `make dt_binding_check` (see
Documentation/devicetree/bindings/writing-schema.rst for instructions).
Maybe you need to update your dtschema and yamllint.
Best regards,
Krzysztof
^ permalink raw reply
* Re: (subset) [PATCH 1/2] arm64: dts: ti: k3-am62p5-sk: minor whitespace cleanup
From: Krzysztof Kozlowski @ 2024-04-09 20:04 UTC (permalink / raw)
To: Nishanth Menon, Benoît Cousson, Tony Lindgren, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Vignesh Raghavendra,
Tero Kristo, linux-omap, devicetree, linux-kernel,
linux-arm-kernel
In-Reply-To: <171269138685.642844.11136653326464585397.b4-ty@ti.com>
On 09/04/2024 21:36, Nishanth Menon wrote:
> Hi Krzysztof Kozlowski,
>
> On Thu, 08 Feb 2024 11:51:45 +0100, Krzysztof Kozlowski wrote:
>> The DTS code coding style expects exactly one space before '{'
>> character.
>>
>>
> As discussed offline, I am picking this patch up.
>
> I have applied the following to branch ti-k3-dts-next on [1].
> Thank you!
>
> [1/2] arm64: dts: ti: k3-am62p5-sk: minor whitespace cleanup
> commit: 45ab8daed512258c07fd14536a3633440dabfe84
What about the omap one (second in the series)? Shall I take it?
Best regards,
Krzysztof
^ permalink raw reply
* Re: [PATCH v2 3/7] dt-bindings: PCI: qcom: Add IPQ9574 PCIe controller
From: Krzysztof Kozlowski @ 2024-04-09 20:08 UTC (permalink / raw)
To: Alexandru Gagniuc, Bjorn Andersson, Konrad Dybcio,
Lorenzo Pieralisi, Krzysztof Wilczyński, Rob Herring,
Bjorn Helgaas, Krzysztof Kozlowski, Conor Dooley,
Manivannan Sadhasivam
Cc: linux-arm-msm, linux-pci, devicetree, linux-kernel
In-Reply-To: <20240409190833.3485824-4-mr.nuke.me@gmail.com>
On 09/04/2024 21:08, Alexandru Gagniuc wrote:
> IPQ9574 has PCIe controllers which are almost identical to IPQ6018.
> The only difference is that the "iface" clock is not required.
> Document this difference along with the compatible string.
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
> ---
> .../devicetree/bindings/pci/qcom,pcie.yaml | 34 +++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> index cf9a6910b542..1915bea580d3 100644
> --- a/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie.yaml
> @@ -26,6 +26,7 @@ properties:
> - qcom,pcie-ipq8064-v2
> - qcom,pcie-ipq8074
> - qcom,pcie-ipq8074-gen3
> + - qcom,pcie-ipq9574
> - qcom,pcie-msm8996
> - qcom,pcie-qcs404
> - qcom,pcie-sdm845
> @@ -397,6 +398,37 @@ allOf:
> - const: axi_m_sticky # AXI Master Sticky reset
> - const: axi_s_sticky # AXI Slave Sticky reset
>
Where do you constrain the reg?
Best regards,
Krzysztof
^ permalink raw reply
* Re: [PATCH v2 5/7] dt-bindings: phy: qcom,ipq8074-qmp-pcie: add ipq9574 gen3x2 PHY
From: Krzysztof Kozlowski @ 2024-04-09 20:09 UTC (permalink / raw)
To: Alexandru Gagniuc, Bjorn Andersson, Konrad Dybcio, Vinod Koul,
Kishon Vijay Abraham I, Rob Herring, Krzysztof Kozlowski,
Conor Dooley
Cc: linux-arm-msm, linux-phy, devicetree, linux-kernel
In-Reply-To: <20240409190833.3485824-6-mr.nuke.me@gmail.com>
On 09/04/2024 21:08, Alexandru Gagniuc wrote:
> The IPQ9574 gen3x2 PHY is very similar to IPQ6018. It requires two
> extra clocks named "anoc" and "snoc". Document this, and add a
> new compatible string for this PHY.
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
> ---
> .../phy/qcom,ipq8074-qmp-pcie-phy.yaml | 31 ++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml
> index 634cec5d57ea..017ad65a9a3c 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml
> @@ -19,19 +19,22 @@ properties:
> - qcom,ipq6018-qmp-pcie-phy
> - qcom,ipq8074-qmp-gen3-pcie-phy
> - qcom,ipq8074-qmp-pcie-phy
> + - qcom,ipq9574-qmp-gen3x2-pcie-phy
>
> reg:
> items:
> - description: serdes
>
> clocks:
> - maxItems: 3
> + minItems: 3
Which binding inspired you to such change? No, you need maxItems. See
your previous patches here how it is done.
>
> clock-names:
> items:
> - const: aux
> - const: cfg_ahb
> - const: pipe
> + - const: anoc
> + - const: snoc
OK, you did not test it. Neither this, nor DTS. I stop review, please
test first.
Best regards,
Krzysztof
^ permalink raw reply
* Re: [PATCH 1/2] dt-bindings: panel-simple-dsi: add New Khadas TS050 panel bindings
From: Krzysztof Kozlowski @ 2024-04-09 20:11 UTC (permalink / raw)
To: Jacobe Zang, neil.armstrong, narmstrong, airlied, daniel,
maarten.lankhorst, mripard, tzimmermann, robh,
krzysztof.kozlowski+dt, conor+dt
Cc: quic_jesszhan, sam, nick, thierry.reding, dri-devel, devicetree,
linux-kernel, linux-amlogic
In-Reply-To: <20240409082641.359627-1-jacobe.zang@wesion.com>
On 09/04/2024 10:26, Jacobe Zang wrote:
> This add the bindings for the New Khadas TS050 1080x1920 5" LCD DSI panel
> designed to work with the Khadas VIM3 and VIM3L Single Board Computers.
>
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
> .../devicetree/bindings/display/panel/panel-simple-dsi.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml b/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml
> index f9160d7bac3ca..e194309f31b72 100644
> --- a/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml
> @@ -36,6 +36,8 @@ properties:
> - jdi,fhd-r63452
> # Khadas TS050 5" 1080x1920 LCD panel
> - khadas,ts050
> + # Khadas NEW TS050 5" 1080x1920 LCD panel
> + - khadas,newts050
Keep things ordered.
Best regards,
Krzysztof
^ permalink raw reply
* Re: [PATCH v2 5/7] dt-bindings: phy: qcom,ipq8074-qmp-pcie: add ipq9574 gen3x2 PHY
From: mr.nuke.me @ 2024-04-09 20:19 UTC (permalink / raw)
To: Krzysztof Kozlowski, Bjorn Andersson, Konrad Dybcio, Vinod Koul,
Kishon Vijay Abraham I, Rob Herring, Krzysztof Kozlowski,
Conor Dooley
Cc: linux-arm-msm, linux-phy, devicetree, linux-kernel
In-Reply-To: <019180df-67b9-438b-a10d-f92fd4ddec03@linaro.org>
On 4/9/24 15:09, Krzysztof Kozlowski wrote:
> On 09/04/2024 21:08, Alexandru Gagniuc wrote:
>> The IPQ9574 gen3x2 PHY is very similar to IPQ6018. It requires two
>> extra clocks named "anoc" and "snoc". Document this, and add a
>> new compatible string for this PHY.
>>
>> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
>> ---
>> .../phy/qcom,ipq8074-qmp-pcie-phy.yaml | 31 ++++++++++++++++++-
>> 1 file changed, 30 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml
>> index 634cec5d57ea..017ad65a9a3c 100644
>> --- a/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml
>> +++ b/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.yaml
>> @@ -19,19 +19,22 @@ properties:
>> - qcom,ipq6018-qmp-pcie-phy
>> - qcom,ipq8074-qmp-gen3-pcie-phy
>> - qcom,ipq8074-qmp-pcie-phy
>> + - qcom,ipq9574-qmp-gen3x2-pcie-phy
>>
>> reg:
>> items:
>> - description: serdes
>>
>> clocks:
>> - maxItems: 3
>> + minItems: 3
>
> Which binding inspired you to such change? No, you need maxItems. See
> your previous patches here how it is done.
>
>
>>
>> clock-names:
>> items:
>> - const: aux
>> - const: cfg_ahb
>> - const: pipe
>> + - const: anoc
>> + - const: snoc
>
> OK, you did not test it. Neither this, nor DTS. I stop review, please
> test first.
I ran both `checkpatch.pl` and `make dt_binding_check`. What in this
patch makes you say I "did not test it", and what test or tests did I miss?
Alex
^ permalink raw reply
* Re: [PATCH v2 5/7] dt-bindings: phy: qcom,ipq8074-qmp-pcie: add ipq9574 gen3x2 PHY
From: Krzysztof Kozlowski @ 2024-04-09 20:28 UTC (permalink / raw)
To: mr.nuke.me, Bjorn Andersson, Konrad Dybcio, Vinod Koul,
Kishon Vijay Abraham I, Rob Herring, Krzysztof Kozlowski,
Conor Dooley
Cc: linux-arm-msm, linux-phy, devicetree, linux-kernel
In-Reply-To: <33461c22-21a3-023b-4750-c69304471ea8@gmail.com>
On 09/04/2024 22:19, mr.nuke.me@gmail.com wrote:
>> Which binding inspired you to such change? No, you need maxItems. See
>> your previous patches here how it is done.
>>
>>
>>>
>>> clock-names:
>>> items:
>>> - const: aux
>>> - const: cfg_ahb
>>> - const: pipe
>>> + - const: anoc
>>> + - const: snoc
>>
>> OK, you did not test it. Neither this, nor DTS. I stop review, please
>> test first.
>
> I ran both `checkpatch.pl` and `make dt_binding_check`. What in this
> patch makes you say I "did not test it", and what test or tests did I miss?
You affect existing bindings, so you must test your and entire existing
DTS. You affect, by introducing new errors, in existing DTS.
Best regards,
Krzysztof
^ permalink raw reply
* Re: [PATCH 12/17] scsi: ufs: host: ufs-exynos: Add EXYNOS_UFS_OPT_UFSPR_SECURE option
From: William McVicker @ 2024-04-09 20:30 UTC (permalink / raw)
To: Peter Griffin
Cc: mturquette, sboyd, robh, krzk+dt, conor+dt, vkoul, kishon,
alim.akhtar, avri.altman, bvanassche, s.nawrocki, cw00.choi, jejb,
martin.petersen, chanho61.park, ebiggers, linux-scsi, linux-phy,
devicetree, linux-clk, linux-samsung-soc, linux-kernel,
linux-arm-kernel, tudor.ambarus, andre.draszik, saravanak
In-Reply-To: <20240404122559.898930-13-peter.griffin@linaro.org>
On 04/04/2024, Peter Griffin wrote:
> This option is intended to be set on platforms whose ufspr
> registers are only accessible via smc call (such as gs101).
>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
> ---
Tested-by: Will McVicker <willmcvicker@google.com>
I tested this patch series on a Pixel 6 device. I was able to successfully
mount two of the Android ext4 partitions -- efs and metadata.
root@google-gs:~# mount | grep /dev/sda
/dev/sda5 on /mnt/efs type ext4 (rw,relatime)
/dev/sda8 on /mnt/metadata type ext4 (rw,relatime)
Regards,
Will
^ permalink raw reply
* Re: [PATCH 13/17] scsi: ufs: host: ufs-exynos: add EXYNOS_UFS_OPT_TIMER_TICK_SELECT option
From: William McVicker @ 2024-04-09 20:31 UTC (permalink / raw)
To: Peter Griffin
Cc: mturquette, sboyd, robh, krzk+dt, conor+dt, vkoul, kishon,
alim.akhtar, avri.altman, bvanassche, s.nawrocki, cw00.choi, jejb,
martin.petersen, chanho61.park, ebiggers, linux-scsi, linux-phy,
devicetree, linux-clk, linux-samsung-soc, linux-kernel,
linux-arm-kernel, tudor.ambarus, andre.draszik, saravanak
In-Reply-To: <20240404122559.898930-14-peter.griffin@linaro.org>
On 04/04/2024, Peter Griffin wrote:
> This option is intended to be set for SoCs that have HCI_V2P1_CTRL
> register and can select their tick source via IA_TICK_SEL bit.
>
> Source clock selection for timer tick
> 0x0 = Bus clock (aclk)
> 0x1 = Function clock (mclk)
>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
> ---
Tested-by: Will McVicker <willmcvicker@google.com>
I tested this patch series on a Pixel 6 device. I was able to successfully
mount two of the Android ext4 partitions -- efs and metadata.
root@google-gs:~# mount | grep /dev/sda
/dev/sda5 on /mnt/efs type ext4 (rw,relatime)
/dev/sda8 on /mnt/metadata type ext4 (rw,relatime)
Regards,
Will
^ permalink raw reply
* Re: [PATCH 14/17] scsi: ufs: host: ufs-exynos: allow max frequencies up to 267Mhz
From: William McVicker @ 2024-04-09 20:32 UTC (permalink / raw)
To: Peter Griffin
Cc: mturquette, sboyd, robh, krzk+dt, conor+dt, vkoul, kishon,
alim.akhtar, avri.altman, bvanassche, s.nawrocki, cw00.choi, jejb,
martin.petersen, chanho61.park, ebiggers, linux-scsi, linux-phy,
devicetree, linux-clk, linux-samsung-soc, linux-kernel,
linux-arm-kernel, tudor.ambarus, andre.draszik, saravanak
In-Reply-To: <20240404122559.898930-15-peter.griffin@linaro.org>
On 04/04/2024, Peter Griffin wrote:
> Platforms such as Tensor gs101 the pclk frequency is 267Mhz.
> Increase PCLK_AVAIL_MAX so we don't fail the frequency check.
>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
> ---
Tested-by: Will McVicker <willmcvicker@google.com>
I tested this patch series on a Pixel 6 device. I was able to successfully
mount two of the Android ext4 partitions -- efs and metadata.
root@google-gs:~# mount | grep /dev/sda
/dev/sda5 on /mnt/efs type ext4 (rw,relatime)
/dev/sda8 on /mnt/metadata type ext4 (rw,relatime)
Regards,
Will
^ permalink raw reply
* Re: [PATCH 15/17] scsi: ufs: host: ufs-exynos: add some pa_dbg_ register offsets into drvdata
From: William McVicker @ 2024-04-09 20:35 UTC (permalink / raw)
To: Peter Griffin
Cc: mturquette, sboyd, robh, krzk+dt, conor+dt, vkoul, kishon,
alim.akhtar, avri.altman, bvanassche, s.nawrocki, cw00.choi, jejb,
martin.petersen, chanho61.park, ebiggers, linux-scsi, linux-phy,
devicetree, linux-clk, linux-samsung-soc, linux-kernel,
linux-arm-kernel, tudor.ambarus, andre.draszik, saravanak
In-Reply-To: <20240404122559.898930-16-peter.griffin@linaro.org>
On 04/04/2024, Peter Griffin wrote:
> This allows these registers to be at different offsets or not
> exist at all on some SoCs variants.
>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
Tested-by: Will McVicker <willmcvicker@google.com>
I tested this patch series on a Pixel 6 device. I was able to successfully
mount two of the Android ext4 partitions -- efs and metadata.
root@google-gs:~# mount | grep /dev/sda
/dev/sda5 on /mnt/efs type ext4 (rw,relatime)
/dev/sda8 on /mnt/metadata type ext4 (rw,relatime)
Regards,
Will
^ permalink raw reply
* Re: [PATCH 16/17] scsi: ufs: host: ufs-exynos: Add support for Tensor gs101 SoC
From: William McVicker @ 2024-04-09 20:36 UTC (permalink / raw)
To: Peter Griffin
Cc: mturquette, sboyd, robh, krzk+dt, conor+dt, vkoul, kishon,
alim.akhtar, avri.altman, bvanassche, s.nawrocki, cw00.choi, jejb,
martin.petersen, chanho61.park, ebiggers, linux-scsi, linux-phy,
devicetree, linux-clk, linux-samsung-soc, linux-kernel,
linux-arm-kernel, tudor.ambarus, andre.draszik, saravanak
In-Reply-To: <20240404122559.898930-17-peter.griffin@linaro.org>
On 04/04/2024, Peter Griffin wrote:
> Add a dedicated compatible and drv_data with associated
> hooks for gs101 SoC found on Pixel 6.
>
> Note we make use of the previously added EXYNOS_UFS_OPT_UFSPR_SECURE
> option, to skip initialisation of UFSPR registers as these are only
> accessible via SMC call.
>
> EXYNOS_UFS_OPT_TIMER_TICK_SELECT option is also set to select tick
> source. This has been done so as not to effect any existing platforms.
>
> DBG_OPTION_SUITE on gs101 has different address offsets to other SoCs
> so these register offsets now come from uic_attr struct.
>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
> ---
Tested-by: Will McVicker <willmcvicker@google.com>
I tested this patch series on a Pixel 6 device. I was able to successfully
mount two of the Android ext4 partitions -- efs and metadata.
root@google-gs:~# mount | grep /dev/sda
/dev/sda5 on /mnt/efs type ext4 (rw,relatime)
/dev/sda8 on /mnt/metadata type ext4 (rw,relatime)
Regards,
Will
^ permalink raw reply
* Re: [PATCH v2 5/7] dt-bindings: phy: qcom,ipq8074-qmp-pcie: add ipq9574 gen3x2 PHY
From: Rob Herring @ 2024-04-09 20:49 UTC (permalink / raw)
To: Alexandru Gagniuc
Cc: Kishon Vijay Abraham I, Krzysztof Kozlowski, linux-phy,
Conor Dooley, linux-kernel, Konrad Dybcio, linux-arm-msm,
Bjorn Andersson, Vinod Koul, devicetree
In-Reply-To: <20240409190833.3485824-6-mr.nuke.me@gmail.com>
On Tue, 09 Apr 2024 14:08:31 -0500, Alexandru Gagniuc wrote:
> The IPQ9574 gen3x2 PHY is very similar to IPQ6018. It requires two
> extra clocks named "anoc" and "snoc". Document this, and add a
> new compatible string for this PHY.
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
> ---
> .../phy/qcom,ipq8074-qmp-pcie-phy.yaml | 31 ++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/phy/qcom,ipq8074-qmp-pcie-phy.example.dtb: phy@84000: clock-names: ['aux', 'cfg_ahb', 'pipe'] is too short
from schema $id: http://devicetree.org/schemas/phy/qcom,ipq8074-qmp-pcie-phy.yaml#
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240409190833.3485824-6-mr.nuke.me@gmail.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox