From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ayush Singh <ayush@beagleboard.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
d-gole@ti.com, lorforlinux@beagleboard.org,
jkridner@beagleboard.org, robertcnelson@beagleboard.org,
Nishanth Menon <nm@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable gb_beagleplay
Date: Mon, 27 Jan 2025 18:41:52 +0100 [thread overview]
Message-ID: <7a576b41-e1bc-4a67-be94-27ada6ec437f@kernel.org> (raw)
In-Reply-To: <20250127-defconfig-beagleplay-v1-1-22a60085e313@beagleboard.org>
On 27/01/2025 13:39, Ayush Singh wrote:
> Enable greybus driver for Ti CC1352P7 over UART.
Which upstream hardware uses it?
>
> The driver communicates with Ti CC1352P7 co-processor which acts as
> Greybus SVC. Additionally, it also provides firmware upload API support
> for Ti CC1352P7 over UART.
>
> Signed-off-by: Ayush Singh <ayush@beagleboard.org>
> ---
> Enable greybus driver for Ti CC1352P5 over UART used in BeaglePlay [0].
>
> [0]: https://www.beagleboard.org/boards/beagleplay
> ---
> arch/arm64/configs/defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index cb7da44155999b59aff95966f4cdc9107f2af46a..24353b0aa3e0ae1786ce99706a52cbf25d037d3b 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1760,3 +1760,6 @@ CONFIG_CORESIGHT_STM=m
> CONFIG_CORESIGHT_CPU_DEBUG=m
> CONFIG_CORESIGHT_CTI=m
> CONFIG_MEMTEST=y
> +CONFIG_GREYBUS=m
> +CONFIG_GREYBUS_BEAGLEPLAY=m
> +CONFIG_FW_UPLOAD=y
Does not look like placed according to Kconfig order (see savedefconfig).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-27 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 12:39 [PATCH] arm64: defconfig: Enable gb_beagleplay Ayush Singh
2025-01-27 17:41 ` Krzysztof Kozlowski [this message]
2025-01-27 18:08 ` Ayush Singh
2025-01-27 18:12 ` Krzysztof Kozlowski
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=7a576b41-e1bc-4a67-be94-27ada6ec437f@kernel.org \
--to=krzk@kernel.org \
--cc=ayush@beagleboard.org \
--cc=catalin.marinas@arm.com \
--cc=d-gole@ti.com \
--cc=jkridner@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorforlinux@beagleboard.org \
--cc=nm@ti.com \
--cc=robertcnelson@beagleboard.org \
--cc=will@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