From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C7323C64ED6 for ; Mon, 27 Feb 2023 07:11:05 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 063E685A26; Mon, 27 Feb 2023 08:11:03 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=amarulasolutions.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=amarulasolutions.com header.i=@amarulasolutions.com header.b="Iu5qLCVb"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id D5A8B85A2E; Mon, 27 Feb 2023 08:11:00 +0100 (CET) Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 0D3A585A22 for ; Mon, 27 Feb 2023 08:10:58 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=amarulasolutions.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=jagan@amarulasolutions.com Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-53852143afcso150380997b3.3 for ; Sun, 26 Feb 2023 23:10:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HItdJbGzWI1fEL2vNWZGuZXacDZZj7xsgg6Eq9tJG0g=; b=Iu5qLCVb/6ED+shxdSvh9av629mgczpeagjgGz2KvDaWGIX0/t7vfpgPa9J8/0JyAO SJdWzC5lGSTzqUxlKwH5rRQcbjReTuSwwEXAfzX1A6yDYEAQuXJPwDHIAFLBlRbL9mCP Tvg0YloIWUVqc4eMFLjsfsx6cLHdZfpQqIOZc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HItdJbGzWI1fEL2vNWZGuZXacDZZj7xsgg6Eq9tJG0g=; b=qzhWFomMNrCVuy+LaOJprliqtE+Y7lybIDESVIIDamJWNoUXsh/X82TyQz6C/iNPa/ ynHf/zM3NllghleSB9425P7ZqqHCjEvuSncjoM0abuVm4YFrZRlHGIKN2sWqioc0EnbU EYcOy6euLdHpbQDnYV6wMeJr1leWlfMG1MR9Q0WGWFsu1xbBQ2BUa6pig//DywTmogLX +0mJ81KUzckFr80PnqajbG2G06kbr1Evs4BvO8Xi0AfOImHWzXggaJxCVj/ka02A01nw 0IJiETJ9ME2wXHtdNnP8hVYs/GfNug4RVvVSGu0rSrJ8EVoRd9eMYh9x/ItMrJUcFKh6 NAbw== X-Gm-Message-State: AO0yUKUKkQYZn2JOBTFPYXSiUrmpP/tFqdzypMaUrss5dwdnYH2GurMm vo/x8Ce74oYEJMvojWhu6FG2aRk/xAYQGoL9EJ4K8A== X-Google-Smtp-Source: AK7set/yU6V4HkBoTAuqjF2sFglqaU3KGbnQ7e+eE74tzZ3kcejYTETMx4DzUXjHNws2QUqoIohPHndBRUE9/Bgt7lM= X-Received: by 2002:a5b:251:0:b0:a6a:3356:6561 with SMTP id g17-20020a5b0251000000b00a6a33566561mr2178561ybp.1.1677481856446; Sun, 26 Feb 2023 23:10:56 -0800 (PST) MIME-Version: 1.0 References: <20220222013131.3114990-1-pgwipeout@gmail.com> <20220222013131.3114990-10-pgwipeout@gmail.com> In-Reply-To: <20220222013131.3114990-10-pgwipeout@gmail.com> From: Jagan Teki Date: Mon, 27 Feb 2023 12:40:45 +0530 Message-ID: Subject: Re: [PATCH v1 09/11] rockchip: move dwc3 config to chip specific handler To: Peter Geis Cc: Simon Glass , Philipp Tomsich , Kever Yang , u-boot@lists.denx.de Content-Type: text/plain; charset="UTF-8" X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean On Tue, Feb 22, 2022 at 7:03 AM Peter Geis wrote: > > The dwc3 code in the mach-rockchip board file is specific to the rk3399. > Move it to the rk3399 chip specific code. Though it is rk3399, there is no new SoC that requires OTG as of now even if needed it is easy to support here instead of moving this redundant on each board file. https://patchwork.ozlabs.org/project/uboot/patch/20230226132234.31949-2-abbaraju.manojsai@amarulasolutions.com/ So, please don't move. Jagan.