Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp4460294ioa; Wed, 27 Apr 2022 04:29:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzUio2vT8gnVgwyl7QTlUT4psSssxGEt/vMGQ+neLTcKux5AYG7T2z8Pj66YlxCHng4fXZS X-Received: by 2002:a63:2d5:0:b0:3aa:f926:3224 with SMTP id 204-20020a6302d5000000b003aaf9263224mr18438699pgc.153.1651058982280; Wed, 27 Apr 2022 04:29:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651058982; cv=none; d=google.com; s=arc-20160816; b=Jj033gv4ccEkQfqUx9kedUGmLb2CrsqDhpzRneeWU8k6El36Jc3JrCTGYVwSP1F6ya QISFj6X6VoXPN5hdZi6NgG6Kf7rS/6zAqKzRt7ABmIsnJnyeQnSkOVTP/xWmA9Zkrori nmnjJwcPLsq4UmDC42IaXyP2N6horfV9q2DzPgIZX8NSFjz7GTalT7eJxi5QesR+VZBU kBc1yExOqy67/zoYdvstAoZC1FjzKnhQhsxTyEI71U3yo8a1YvkE8C44mF5ukYEuFHNw 3vB/6fZGZn+y1TM2xME/0V9LRYpOWypkvUk8EHTChtpRq/QOOU9nloNm1ZOi0MYYArwB egeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:user-agent:from :references:in-reply-to:mime-version:dkim-signature; bh=MWHv2TFewrJAPnTOlW4qxlIxjpJGKW/g1lpO6FHxMAU=; b=GlpeKoV/RosDo1HHGPPulp1YG60o33l5BA+6gt3p4Yo0JZ8HBkofgmUBCxv/q5fl8a GG/5hFHAuvEOpIsJMejsgpL3EsmyytKAb/bB0mWS85PE1YHdea1bj/1km1Z2HVHdpLvw n5IjqzZJH+Jc/N2ZnuzybW2fmjnLoIHbznFU90RgSPWNoxPSqDuJLlKnnyj6DEV2R5vt 1CLdKGlmAbn5vFG9j/nTt9djlg782neUtG+8UNzNMEB+9Gt6Im3uEDoS6BLYsUljDSXf 9fMP9IUxJHx8nBlmkT0LsGC/Cx96ZHSMvGRPlVzYbF20BmxWEPmmiVoEtmUP8tKp6uli OiIA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=mpzPEMET; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id om13-20020a17090b3a8d00b001d242c15065si5148848pjb.123.2022.04.27.04.29.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Apr 2022 04:29:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=mpzPEMET; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D5D14219D; Wed, 27 Apr 2022 03:17:23 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355373AbiDZVXA (ORCPT + 99 others); Tue, 26 Apr 2022 17:23:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54876 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1355369AbiDZVW5 (ORCPT ); Tue, 26 Apr 2022 17:22:57 -0400 Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0F2DC8BCD for ; Tue, 26 Apr 2022 14:19:47 -0700 (PDT) Received: by mail-ot1-x32f.google.com with SMTP id s21-20020a0568301e1500b006054da8e72dso13954936otr.1 for ; Tue, 26 Apr 2022 14:19:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:in-reply-to:references:from:user-agent:date:message-id :subject:to:cc; bh=MWHv2TFewrJAPnTOlW4qxlIxjpJGKW/g1lpO6FHxMAU=; b=mpzPEMETgbUkrlArfjYnb6ZpqroDw1mZAkpGqiBB5PVb8cmmQ01gcb3oyxdNlLfPAK nRTKFA5C3mK0kiSXAA6f+Oai3vDQMqoLiwrSZ8SL7jDgzbvo5scQZePIJ+ldIeuGYEst pzjRUCWOBhnGjrLKOYtmAvWh95ioiy9ZfJ6Lg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from :user-agent:date:message-id:subject:to:cc; bh=MWHv2TFewrJAPnTOlW4qxlIxjpJGKW/g1lpO6FHxMAU=; b=KvQCUM+kYV10pEc7eyrLQUKwpzEtqE3R3uzWhNx0xTKngPUgeVXiJwVH7qUmTg4nis KAhZrkvgKRcA9Sg5oi8cD1QDnMjsszI1iU5+Aa2cBgvMs+fyIeCehDxdsdOEXe8qRtl2 DctxtpHVRw9an0NkDyR+UjR4b1bKpO5i3alqzR0ocZC79vlN88YQAV1xuoCD55Is2/LS /Gc9pgP6BiQYJcVfmHOoaVncx5+Vjdww7ihwJZ49jbRDp5ONTcnA9EBzW7h1xcMeuAsM qPlyq00gEgg5eek0QA9GQ4MZzqThulHbCw0UVHyhW0iRBljOdmGeSPeMLCot0KDlKhDW /aWg== X-Gm-Message-State: AOAM532CDzoLp+vghwR1oLEDrN0ohx9iSB6OxwXPuJMfp3VOjjmaJnpW /nGENmP2cCieXwBm9GHrCyO4TWDAVew482NPT4Qdpw== X-Received: by 2002:a9d:20a1:0:b0:5e8:d2b6:f63f with SMTP id x30-20020a9d20a1000000b005e8d2b6f63fmr8859832ota.159.1651007987265; Tue, 26 Apr 2022 14:19:47 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Tue, 26 Apr 2022 14:19:46 -0700 MIME-Version: 1.0 In-Reply-To: <20220426124053.v2.1.Iedd71976a78d53c301ce0134832de95a989c9195@changeid> References: <20220426124053.v2.1.Iedd71976a78d53c301ce0134832de95a989c9195@changeid> From: Stephen Boyd User-Agent: alot/0.10 Date: Tue, 26 Apr 2022 14:19:46 -0700 Message-ID: Subject: Re: [PATCH v2] arm64: dts: qcom: sc7280: eDP for herobrine boards To: Bjorn Andersson , Douglas Anderson Cc: Dmitry Baryshkov , Kuogee Hsieh , Rob Clark , linux-arm-msm@vger.kernel.org, Sankeerth Billakanti , Abhinav Kumar , quic_kalyant@quicinc.com, Matthias Kaehlcke , Andy Gross , Krzysztof Kozlowski , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Douglas Anderson (2022-04-26 12:41:03) > Add eDP support to herobrine boards, splitting up amongst the > different files as makes sense. Rationale for the current split of > things: > * The eDP connector itself is on qcard. However, not all devices with > a qcard will use an eDP panel. Some might use MIPI and, presumably, > someone could build a device with qcard that had no display at all. > * The qcard provides a PWM for backlight that goes to the eDP > connector. This PWM is also provided to the board and it's expected > that it would be used as the backlight PWM even for herobrine > devices with MIPI displays. > * It's currently assumed that all herobrine boards will have some sort > of display, either MIPI or eDP (but not both). > * We will assume herobrine-rev1 has eDP. The schematics allow for a > MIPI panel to be hooked up but, aside from some testing, nobody is > doing this and most boards don't have all the parts stuffed for > it. The two panels would also share a PWM for backlight, which is > weird. > * herobrine-villager and herobrine-hoglin (crd) also have eDP. > * herobrine-hoglin (crd) has slightly different regulator setup for > the backlight. It's expected that this is unique to this board. See > comments in the dts file. > * There are some regulators that are defined in the qcard schematic > but provided by the board like "vreg_edp_bl" and > "vreg_edp_3p3". While we could put references to these regulators > straight in the qcard.dtsi file, this would force someone using > qcard that didn't provide those regulators to provide a dummy or do > an ugly /delete-node/. Instead, we'll add references in > herobrine.dtsi. > > Signed-off-by: Douglas Anderson > --- Reviewed-by: Stephen Boyd