From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E2D331E22E9 for ; Wed, 11 Feb 2026 04:39:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770784751; cv=none; b=RZGvRSUUWy0yhXf4Tow7rp59UfsFb+zaLHd6SR1VSpqu/nrVRwHsdDbPZ9YKB9uIfH5VZl2pHZ7hMI0VhIOjwRhTFMnD7nN8JLgAPvGot/8vIMaiqNuJHtpJ/IpRykQMiy/R1uDBUq2sbVjMElUCm/VMVjvo6SAeEVMj3mcbhlM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770784751; c=relaxed/simple; bh=GmV3/8os27+VDc7hRFwfdSxvPO0Dri934t1jCbcEIPM=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=jHOa8ZkS0716xWV8N8bkfM0zm9nTHawr7/qZ+E8fIhhGlbSmC7NTp9wtfQLKoLxzppFxOvZhJX8s93kFPf6q123apITXlt5dB6jpgjsttDo/chO/mCTxl/9yCHd7XPjhz1GwAvmuvgALJ94TfP2owAeBU+bMCeFX7Tv0P4wUdEM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=W8C6iAeh; arc=none smtp.client-ip=209.85.210.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="W8C6iAeh" Received: by mail-pf1-f182.google.com with SMTP id d2e1a72fcca58-81df6a302b1so5326246b3a.2 for ; Tue, 10 Feb 2026 20:39:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1770784749; x=1771389549; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=RYskh5BzGqN670gcx9isWJs2ERD0SiYbFu/I54K8Bvo=; b=W8C6iAehA8HkoeUvBrOJb8R1TdjC1wexV6EpLvNdIR+PKZSQWmFR+73SUZHS2Co7V6 J5w9KXkbABUjfWlN/tSrnkBaeunB7iyiR555SE29tS5ZMcPWDE88x8nK4kRsL/+D4iRy 5H3g/DA1hr/VPONda8AYjYNhqs0hOAsgdHQDuSmxSndJMHuc7sYuNUS6IpBpP9PaLXjz 7pNQ9Ekd0BIBdkdJWCzY64WDPVbjVqBf/zl/IPSejGscQV9laej2R0lqC+oK9Ug+ax39 7IQGL9Z0o4nb7sUIL8dDxlQAvp1McDuy/6ci97zhk6GrkGkAuKbqCnRk9yZA3IADj8Oy GFYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770784749; x=1771389549; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RYskh5BzGqN670gcx9isWJs2ERD0SiYbFu/I54K8Bvo=; b=Vppj2yaA7LkTjLf47Sm9DldyFe+tzsSLm57umRD5hsf8ldYVAoZz+hAXqiaLhuyszm 59dcSHDaaYNN1joFSwPp1AsGn+0rP50lDRazbJ2/cJHKES8ekFMpAAMc4AYWlYxJ8uto fGt93kwYa2k1MoilMBoqBEV//q9xj/1x/RzPHVXPcz1mM+gp1fejL3qZGg5TXFwM5bx0 v96lIRoLx7YEpHdFs3kl6UKL+XSdopgO8niaJEz/7GmgxK3pb6s9kzY/7C60EVHlcLmr nTj4H3EGCKCg4KrRNXiFvnZwgfkR6A1cVcOOA41D097acTvgObrsPTW0K+T3LXutf6h8 9rWg== X-Forwarded-Encrypted: i=1; AJvYcCWof3nttZIwSbdze1FV/Q1ELYPzzxbY5jZ0pFTHOzkiAMidO3+L2FPlHhWCG8elQ59z3oiQFYiCNPftljo=@vger.kernel.org X-Gm-Message-State: AOJu0YwnM6bQvq3XahQ7sPuxN9m4XCS2aiq3YtQSh7wXWHpgNQPYhP6I jBMR5jWeZKEkl8gl2MN7yzIavhzATyXzzD64TEXa3UpdR3f3UKBgyTY1 X-Gm-Gg: AZuq6aLdP0NHGDncvgzF+SIEh+i3sduHGSXek8N7E8uF3FFVP1n6kTRWzA2BYFLeobI MaGQbN67kcj3HwcJ//Qis+TC716zb6MHmJHc5BsIADlHpzOed8qj5OAFRG7bASDfTWMR25MdnKA zWGUxRkqBzLNAbI8d0jUJ0DGCZ4xxf6YDsiUuToZaOjb3tb9YWSSgeDqU6uqWcyxKryC+7dyqaG 40tjyNEWF0ehZEdz7hdHE7d7vyhkFdqk1VQ1ukPrDt+92qXHqcCc/Jsl7iq6+3TlraxPGkSg+KI RkDVXAds64a0GBSYs/UxHCgRsY1++bkuJj9NVxNroJtGWiczCV4zWgnIf/SZy4MUc9lRDlOWGv/ Y1YtYTi+sczwkrbil1F6CVsEQ+7OHACi/4DTciauQ+lvpfTR7X+3v1aiDNTVh1VLrH8/kr5J+YW TvtlZbmrfBYmxoUi4C7LZ+OxD0bddHynShF0BNlfiMIU3m9A== X-Received: by 2002:a05:6a00:37c4:b0:81f:9b09:ad02 with SMTP id d2e1a72fcca58-8249ae2c08cmr1158819b3a.1.1770784749153; Tue, 10 Feb 2026 20:39:09 -0800 (PST) Received: from [172.16.20.12] ([136.226.253.21]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-8249e7d78dcsm608232b3a.31.2026.02.10.20.39.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Feb 2026 20:39:08 -0800 (PST) Message-ID: Date: Wed, 11 Feb 2026 10:09:31 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v12 3/3] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board To: Dmitry Baryshkov Cc: Jie Gan , andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20260114100043.1310164-1-tessolveupstream@gmail.com> <20260114100043.1310164-4-tessolveupstream@gmail.com> <5102252a-0f50-4ee9-97b4-a90859a33b2b@oss.qualcomm.com> <128a5f86-dd3f-4e5e-a55f-3c8b5993779b@gmail.com> <5c5oalpne2xedc42yomtur3lo7vvdyncgs7yd46xw4nvi6pzbd@vcjz3wsyjd3c> <2c59e43f-aee1-4ddb-88dc-1bbf6287c926@gmail.com> Content-Language: en-US From: tessolveupstream@gmail.com In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 04-02-2026 08:28, Dmitry Baryshkov wrote: > On Thu, Jan 29, 2026 at 02:41:25PM +0530, tessolveupstream@gmail.com wrote: >> >> >> On 16-01-2026 13:24, Dmitry Baryshkov wrote: >>> On Fri, Jan 16, 2026 at 11:25:50AM +0530, tessolveupstream@gmail.com wrote: >>>> >>>> >>>> On 15-01-2026 07:54, Jie Gan wrote: >>>>> >>>>> >>>>> On 1/14/2026 6:00 PM, Sudarshan Shetty wrote: >>>>>> Add the device tree for the QCS615-based Talos EVK platform. The >>>>>> platform is composed of a System-on-Module following the SMARC >>>>>> standard, and a Carrier Board. >>>>>> >>>>>> The Carrier Board supports several display configurations, HDMI and >>>>>> LVDS. Both configurations use the same base hardware, with the display >>>>>> selection controlled by a DIP switch. >>>>>> >>>>>> Use a DTBO file, talos-evk-lvds-auo,g133han01.dtso, which defines an >>>>>> overlay that disables HDMI and adds LVDS. The DTs file talos-evk >>>>>> can describe the HDMI display configurations. >>>>>> >>>>>> The initial device tree includes support for: >>>>>> - CPU and memory >>>>>> - UART >>>>>> - GPIOs >>>>>> - Regulators >>>>>> - PMIC >>>>>> - Early console >>>>>> - AT24MAC602 EEPROM >>>>>> - MCP2515 SPI to CAN >>>>>> - ADV7535 DSI-to-HDMI bridge >>>>>> - DisplayPort interface >>>>>> - SN65DSI84ZXHR DSI-to-LVDS bridge >>>>>> - Wi-Fi/BT >>>>>> >>> >>>>>> + >>>>>> +&usb_1 { >>>>>> +    status = "okay"; >>>>>> +}; >>>>>> + >>>>>> +&usb_1_dwc3 { >>>>>> +    dr_mode = "host"; >>>>>> +}; >>>>>> + >>>>>> +&usb_hsphy_1 { >>>>>> +    vdd-supply = <&vreg_l5a>; >>>>>> +    vdda-pll-supply = <&vreg_l12a>; >>>>>> +    vdda-phy-dpdm-supply = <&vreg_l13a>; >>>>>> + >>>>>> +    status = "okay"; >>>>>> +}; >>>>>> + >>>>>> +&usb_2 { >>>>>> +    status = "okay"; >>>>>> +}; >>>>>> + >>>>>> +&usb_2_dwc3 { >>>>>> +    dr_mode = "host"; >>>>>> +}; >>>>> >>>>> Both usb devices have been configured to host mode, do we need adb? >>>>> The adb only work with usb peripheral mode. >>>>> >>>> >>>> This topic was discussed previously, and the fix was implemented >>>> based on that discussion. >>>> For reference, I’m sharing the earlier communication in the >>>> links below. >>>> >>>> https://lore.kernel.org/all/qq4aak33bn3mqxd2edu6zgkkshby63mmitg7zqkly2rj4c2lh7@4s7sndb7e2jr/T/#meaa464a4e6992b36b5d8d41ddc691ee4ea36b1ce >>>> >>>> https://lore.kernel.org/all/20251014120223.1914790-1-tessolveupstream@gmail.com/T/#t >>> >>> Neither of these links is relevant to the question. >>> >> >> In our hardware design, the USB0 controller is a USB 3.0-capable >> controller whose high‑speed (HS) differential lines are routed through >> a mechanical switch. >> >> a) During EDL (flashing) mode: >> The HS lines are explicitly routed to the Micro‑USB port. >> This allows the SoC to enter "device mode" for firmware flashing. >> >> b) After EDL completes (normal operation): >> The mechanical switch is driven to route the HS signals to the on‑ >> board USB 3.0 hub. >> The hub connects to four Type-A ports, all designed for host mode >> only. >> The Micro-USB connector is now electrically disconnected. >> >> Why host-only mode: Once the switch routes to the hub, there's no >> electrical path back to the Micro-USB port. The USB controller can >> only talk to the hub and its downstream Type-A ports, which are wired >> for host mode only. Device mode is physically impossible in this >> configuration. >> Therefore, USB0 must be configured as host-only in the device tree, >> since device mode cannot work after the system boots. >> >> The USB1 controller supports USB 2.0 and has its data lines directly >> routed to a Type-A connector. This hardware design restricts the >> controller to host-only operation, preventing any peripheral/device >> mode functionality. > > Please add a comment regarding EDL-mode DIP switch and describe the > onboard HUB in the DT. Additionally consider adding the USB-peripheral > overlay, corresponding to the EDL-mode configuration as some labs will > not trigger the DIP switch at runtime and settle with the > peripheral-only setting for the USB controller. > Okay, got it. Will take care in the next patch.