Received: by 2002:a19:ef0c:0:0:0:0:0 with SMTP id n12csp951126lfh; Tue, 1 Feb 2022 12:53:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJxwe6OGU1RE1lPh0PCVpq7i4belRm0cbn7LOIqOmyfwIYyZWmdAR4163fZpfQWHOnW7DAvn X-Received: by 2002:a62:1d4a:: with SMTP id d71mr26626908pfd.46.1643748819930; Tue, 01 Feb 2022 12:53:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643748819; cv=none; d=google.com; s=arc-20160816; b=C0WLvH47WYA6zWBOJcHG/vSI7e55jc4yQU3tL9JzgW/EhbrNUWT6d2h1T8Jin8ghpG NT99Sh5Q6iIEXfEGClhi1Yfo5lt5zYSOsgMISwM2ucGX3bmnVpJBR7NoGEERABIwNFpu 4+BnfJcz/y9oMv0TFtRkzqj2XarsyyD8554URnHGIoex9d+YM0lczKo/ULz2XujztPoA PHKBKZrRlqr/oBvPIFUXpYG7inXBE1rTpGruxCO6FUHGjhcjjNGxZaIGJLVbGeXvYso+ nOV6+nCnqfhm8+GXGpv8t7JaMQFjaFetqWbuSSjd+LcUx1VaGxejf3gY9uYaLBMAaAt0 hrZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=PrT+G3tPg9tF+5XuIAQ32IRnOTQfqMCqOg72JDwqGHg=; b=G/30ONF1w+JBxG4KfcKg7Auq4tswfYWs3/AK7HZwSGXzMsx5liSNBeWkUPi/1sad9m SFymmA97Gwvadsip+JGj1jN2UXOtM1ZWBGkbEpMSPmiM+dKnQQtjhDxAUBQoVSbeUWX+ 8DRO0dE0d3y/YvhiiPjROl7I9Sos/FsQYMpu6D36eGPIWg5WxaK1TcAy7a+om0zThc2j 53LfcErwY5FYAQTWBjUztT83Z6cmaSV87O/WXBdEE+3YuiemDKEppABBknQvC1vsV+AB Onbcu6hsxxTPiE9O4AR6HxQJtexgkPQUaJkq31D2d7K3Xuhddxq+mFrHC8uAZKy9onPr B8pw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=higE1g8R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w190si10589278pgd.749.2022.02.01.12.53.28; Tue, 01 Feb 2022 12:53:39 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=higE1g8R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229624AbiAaXVs (ORCPT + 99 others); Mon, 31 Jan 2022 18:21:48 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:59725 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238116AbiAaXVr (ORCPT ); Mon, 31 Jan 2022 18:21:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643671305; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PrT+G3tPg9tF+5XuIAQ32IRnOTQfqMCqOg72JDwqGHg=; b=higE1g8RBLhn4JLthHt4+p/oJk3aMk+sXfP3A4c2XCW1IdlK78QTTFhbrsZuoW/GHHcWkE rlbm5YOUeBbnpiaHKs/pj5tmRum/e4FWWplPu5tNeydZnrIqGVLzD7Y8w1UTd6mOvO7v9B mZ8WjdXL9qJ+uUS6im84+L6zFDl4Kkw= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-64-L0vcv8bbOYqtCHXIoKvIlQ-1; Mon, 31 Jan 2022 18:21:44 -0500 X-MC-Unique: L0vcv8bbOYqtCHXIoKvIlQ-1 Received: by mail-wm1-f69.google.com with SMTP id o194-20020a1ca5cb000000b00350b177fb22so427817wme.3 for ; Mon, 31 Jan 2022 15:21:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=PrT+G3tPg9tF+5XuIAQ32IRnOTQfqMCqOg72JDwqGHg=; b=xwmRmNJPpMCIL1EfLp43DFxMFp/ICX2M+c7piBxbHSzMlwFdUkgLekZizTDGxt1yRF sL6j05XdS003iczvCVIufwsdUSvaX9dKaMullN3NftA0adqN2DPIS2VcXkh8zHelyfIK XPmROKRd9f3+6kmQbokoviT+z4jlxaKPEykdAONrdvVB9bOejIq1y1TETRul/XAguOGO 21MOx5TMc1J+FkT2KWXvPRJGqWrv8DzrWM3y1xBabDq2CbIzVERMNbfWt4Ra+GAjlx86 UonO5rpQuyMb7tEE1VgesVOLOnj8xH7Ny6xb3dON68qDQ9RtBJp1R05jojo3bZIRu6Oz a/dA== X-Gm-Message-State: AOAM531NEe6Dy9k26+52mbJ32BnNuvBcEs6ZbiKcmdcPJJ51rBLGypTK /ZSDIFi5oywzHxVd0mE8ucdjkzV6YO+pI+asRJxV4RhHWf6vst3mPPMOMkeKTjR/j1+mfvWFFQQ NF+ROod50lfL9Y2di6QpR7sXJ X-Received: by 2002:a7b:c44d:: with SMTP id l13mr28332779wmi.46.1643671303289; Mon, 31 Jan 2022 15:21:43 -0800 (PST) X-Received: by 2002:a7b:c44d:: with SMTP id l13mr28332767wmi.46.1643671303032; Mon, 31 Jan 2022 15:21:43 -0800 (PST) Received: from [192.168.1.102] ([92.176.231.205]) by smtp.gmail.com with ESMTPSA id p3sm515814wmq.40.2022.01.31.15.21.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 31 Jan 2022 15:21:42 -0800 (PST) Message-ID: Date: Tue, 1 Feb 2022 00:21:41 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH 0/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Content-Language: en-US To: Simon Ser Cc: linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org, Thomas Zimmermann , David Airlie , Daniel Vetter , Mark Brown , dri-devel@lists.freedesktop.org, Liam Girdwood , =?UTF-8?Q?Noralf_Tr=c3=b8nnes?= , Geert Uytterhoeven , Maxime Ripard , =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?= , Thierry Reding , Andy Shevchenko , Lee Jones References: <20220131201225.2324984-1-javierm@redhat.com> From: Javier Martinez Canillas In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Simon, Thanks for your feedback. On 1/31/22 21:39, Simon Ser wrote: > On Monday, January 31st, 2022 at 21:36, Simon Ser wrote: > >> This driver only advertises XRGB8888 in ssd1307_formats. It would be nice to >> expose R8 as well so that user-space can directly produce suitable buffers. >> It would also be nice to have some kind of preferred format, so that user-space >> knows R8 is preferred over XRGB8888. > > Hm, since the format used by the hw is actually R1, adding that to drm_fourcc.h > would be even better. > Yes, agreed that would be nice. We discussed this already with Thomas and my suggestion was to land the driver as is, advertising XRGB8888. Which is also what the other driver using monochrome does (drivers/gpu/drm/tiny/repaper.c): https://www.spinics.net/lists/dri-devel/msg331328.html As a follow-up we can wire up al the needed bits to have a DRM/KMS driver that could expose a R1 format. > Let me know if you want me to type up any of the user-space bits. > Thanks! I also could help to add the needed support in the user-space stack. Best reagards, -- Javier Martinez Canillas Linux Engineering Red Hat