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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 823CEC4743C for ; Fri, 4 Jun 2021 23:19:48 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 437C761359 for ; Fri, 4 Jun 2021 23:19:48 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 437C761359 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 979DF6F59F; Fri, 4 Jun 2021 23:19:47 +0000 (UTC) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) by gabe.freedesktop.org (Postfix) with ESMTPS id A21376F59F for ; Fri, 4 Jun 2021 23:19:45 +0000 (UTC) Received: by mail-lf1-x129.google.com with SMTP id a2so16391483lfc.9 for ; Fri, 04 Jun 2021 16:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kOhQyU7zGziShp3NbADCB7cFUwMTl2wSKNvhDlD5IRs=; b=N1YXPbjsSml+e7RYPDpm05eswG5mLHLOfIJg4btWkRGfg6ucoNdUpmlMe4YjbQyW8d gP6wtg65wOEIVbomYH1bqgtic+hGt3E7X3CIQijUo7IniIzShrQBz2oNySTXgIPYdFu2 YXiNUbMvl9qhYEWLoQhTsMrDN42Z1m4E4SWLD7CHHLsNFKiihmTmgykYZnpDP/BfzV6n fr+VT2TiUYDVMz/lRNlnLjgNvC6FfKYY8wLp7CECSBXVukcwhJGJct9JgHNbyoz5RRU4 /9zqMQdn+0iLKS3lyIo68K9FXquPtPtecwWrgKguWNtK1LgIi0jUgreBmJUvXL4c35Hq yDMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kOhQyU7zGziShp3NbADCB7cFUwMTl2wSKNvhDlD5IRs=; b=pwyKODA84T5TNsWFgS9QrWLt9pzkmPGVATJWjsyg8/Ww1q+wHUKm1qD6bxkpCL6X8P fwT8Eb+4jUz/u99P6ly/4VZzBdgHg/rjrda7VpZqhaOua2LYURGsEMKRgsmzeZKfVNQk G4y4/uiYj9CdfgDnyXsrOvkL82TDvIeF3LWsfVBNw+uJyJrFqdM2U9+Xe32/0ZUSiwhL R+F+DSctd5ejboJCJIIsK92bXZS7e/HyR3qHYy0syxzFxKxFNnMkQewxqL08Jnz94KGA 3AAmYVzTB4dSUIjSHTru1yKl7MSgXpdNKanfhJ2Dw5ebCIq8rBxOjJenq4Cxnbw0QDsv L9+g== X-Gm-Message-State: AOAM5337Dr1yQw1exoKkUaLgvX+KD8BPICXWBmhBS8lvkKMeLZALksHA 7LCMbY/x8hBQIGf4hMNflMVoCwPpM0JrBezLc6JA0g== X-Google-Smtp-Source: ABdhPJxN/ChFWzxD8UT43gX3J+QI6N6IH8Jko8/jscLq8VJGDr8PRWjw74HWQbjs0Src+hv/Xbuy5foc/7NYH/Aa4Jg= X-Received: by 2002:a05:6512:3241:: with SMTP id c1mr4393879lfr.29.1622848783804; Fri, 04 Jun 2021 16:19:43 -0700 (PDT) MIME-Version: 1.0 References: <20210531102838.2423918-1-linus.walleij@linaro.org> In-Reply-To: From: Linus Walleij Date: Sat, 5 Jun 2021 01:19:32 +0200 Message-ID: Subject: Re: [PATCH v2] drm/panel: db7430: Add driver for Samsung DB7430 To: Doug Anderson Content-Type: text/plain; charset="UTF-8" X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Thierry Reding , Sam Ravnborg , dri-devel Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Tue, Jun 1, 2021 at 11:31 PM Doug Anderson wrote: > Still hoping that this can work atop DBI so we can avoid the raw SPI > writes. You said you're trying for it for v3 so I'm looking forward to > checking it out there. Struggling with this. The DBI bus is only used by tiny DRM for the panel drivers that are jitted with that display controller ATM. No normal panel driver is using it. > panel-simple also sets the bpc in the "display_info". Do you need to? > > I didn't see a reply, so I'm still curious about the answer. I think it depends on whether the display controller/bridge actually make use of this or not. It is implied from the MEDIA_BUS_FMT* in practice and this controller (MCDE) only had settings for BPP, no fine grained bits to fiddle for BPC. But I added it for completeness, why not! Who knows who else will come along. I think I should patch a few other drivers with this as well. Yours, Linus Walleij