Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp876223pxb; Tue, 1 Feb 2022 12:14:17 -0800 (PST) X-Google-Smtp-Source: ABdhPJzEZTVL7Lgbczm8Uzs4epZeVlDIIGK80R+IFQ7Y1LWg6qjZSDUMBrh5hZM8U1u85mSnHJX+ X-Received: by 2002:a05:6a00:8d2:: with SMTP id s18mr26165815pfu.5.1643746457615; Tue, 01 Feb 2022 12:14:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643746457; cv=none; d=google.com; s=arc-20160816; b=dzqN83bfltwOmbLi4ZaRkqA8JOono03B65/3Ovb9rX2tPwcfZtYEhzNeEjFes+Rvhb NhU5KL/2yonlh95JH1/woaCmL3cWnRiqv9XQ1GukC3u3Tj0tAUVmJHnla1EimyHgFAih udsvfd2VHx+KGhBvBoMALb9uFdZ0DqeyIkiKINGY5pHwzDMfwuQO5G40lpdmcotEe0iE 6XBROY1f31DsDEurE++g7qGisrSSyVgbnm5tYX0zaMY59uPucWHl9bIug+UzGcLE6W9P aIfq0dPamfsUCuiTFYDKD5k3DxDaqGJgW/cpzEAXZb89/Bt/yR+mwUy4C2ICuKnKOciZ khDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=Ykonzdck5a1Dju7KRT5tnz4w+jMMGab/wE4xgrjjvkM=; b=dizcL2P8VjUQ77xN9Y8zXV7nQnKLlc76fLz1/kW1APjcljMiVXAUm+KrfCpuDEXxp4 UtwMC3I/uOwiFndeTSlfzPUBrwvrZV/+v9urxOJUu5GfUV8XEyXGjs5T8hYJ3ixlSpQ2 x7sJDCCVD9laQcCLH/MUeef9cjOV46BdJh8hlhiPbAJOo6/UxoX3f7fXP66EK+z9tEai 2b060g/r1TFnsH3julIXXyAXc02oV/NActZ7LWEuQSWZORZlK7j+zPYI/IHwopFedq5/ /L9DpJjpgDXL8Z39fliwWkU3SydMyWyw+v2EZS5vmWBgUN9rk3q/E4YCe0qxZg8XDvjv bIig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FOt930E8; 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 22si16853031pgc.486.2022.02.01.12.14.06; Tue, 01 Feb 2022 12:14:17 -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=@intel.com header.s=Intel header.b=FOt930E8; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377452AbiAaLte (ORCPT + 99 others); Mon, 31 Jan 2022 06:49:34 -0500 Received: from mga05.intel.com ([192.55.52.43]:12109 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1379079AbiAaLie (ORCPT ); Mon, 31 Jan 2022 06:38:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643629114; x=1675165114; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=lI9J06ShMDzX4snLdMSWm2sVJLb4bsM0sL6ARCPRO8s=; b=FOt930E8Q1AfSd0j7ONGBh91vtdCIMnhKjdvTbf6oDSE09xeKyr+Eh5m o3qNDf9mi+5B0lXzR57NCz+jiwz38Ppcea8lY37ILBwMBWGzFO0c9vcCi sueCfP9qfqNBH4ec3CE0iSHTGkGI1QcyUN8zvpFNvtZ+MtKMukWRQxktx Kgzh+d4waUcVxophQCSRN8gqbdmeLuDaq4OYdOwS/irPa16fxH5/nmbtR WY6FmXK5PWs1K0pJWmStU/5sI744Wf8A2eULXdL9iwkQ3a4VROMCvP3Ak eIuCDT+GzEesg0D5CHRlTaHjQAw8CtM3xPWuRKzWz2Rqi1ctAWdbVu7+y A==; X-IronPort-AV: E=McAfee;i="6200,9189,10243"; a="333800323" X-IronPort-AV: E=Sophos;i="5.88,330,1635231600"; d="scan'208";a="333800323" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jan 2022 03:37:34 -0800 X-IronPort-AV: E=Sophos;i="5.88,330,1635231600"; d="scan'208";a="619355861" Received: from smile.fi.intel.com ([10.237.72.61]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jan 2022 03:37:31 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nEUyx-00Gqnl-AM; Mon, 31 Jan 2022 13:36:27 +0200 Date: Mon, 31 Jan 2022 13:36:26 +0200 From: Andy Shevchenko To: Javier Martinez Canillas Cc: Greg Kroah-Hartman , Andy Shevchenko , linux-fbdev@vger.kernel.org, Michael Hennerich , Helge Deller , linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Phillip Potter , Carlis , Lee Jones , Heiner Kallweit Subject: Re: [PATCH v1 1/4] fbtft: Unorphan the driver Message-ID: References: <6e74d4cc-655a-e38e-0856-a59e4e6deb36@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 31, 2022 at 09:29:33AM +0100, Javier Martinez Canillas wrote: > On 1/26/22 15:15, Javier Martinez Canillas wrote: > > On 1/26/22 15:10, Andy Shevchenko wrote: > >> On Wed, Jan 26, 2022 at 04:08:32PM +0200, Andy Shevchenko wrote: > >>> On Wed, Jan 26, 2022 at 02:46:08PM +0100, Javier Martinez Canillas wrote: > >>>> On 1/26/22 14:12, Andy Shevchenko wrote: > >> > >> ... > >> > >>>> I've just bought a SSD1306 (I2C) based one and will attempt to write a DRM > >>>> driver using drivers/staging/fbtft/fb_ssd1306.c as a reference. > >>> > >>> You should take ssd1307fb.c instead. And basically create a MIPI based driver > >>> for I2C. Then we won't go same road again for other similar devices. > >> > >> For the record it supports your device: > >> > >> static const struct i2c_device_id ssd1307fb_i2c_id[] = { > >> { "ssd1305fb", 0 }, > >> { "ssd1306fb", 0 }, > >> { "ssd1307fb", 0 }, > >> { "ssd1309fb", 0 }, > >> > >> > > > > Thanks a lot for the pointer. I was only looking at drivers/staging > > and didn't check drivers/video. I'll try to convert that one then > > once I get the display. > > > > I got some time this weekend and was able to port the ssd1306 fbdev driver > to DRM [0]. I'm not that familiar with the simple display pipe helpers, so > there may be some wrong things there. But it does work and all the fbtests > from https://git.kernel.org/pub/scm/linux/kernel/git/geert/fbtest.git pass. Thanks! Good news, everybody! > There are some hacks in the driver though. For example it exposes an XRGB8888 > format even thought the OLED display is monochromatic and has 1 bit per pixel. > > The driver then goes and converts the XRGB8888 pixels first to grayscale and > then to reverse mono. I took that idea from the repaper driver but that gives > us the multiple copies that Geert was complaining about. > > Another hack is that I am just hardcoding the {width, height}_mm, but I don't > know what DPI could be used for these panels nor how I could calculate the mm. I think the hacks is the first what should be eliminated, also see below. ... > +config TINYDRM_SSD130X > + tristate "DRM support for Solomon SSD130X OLED displays" > + depends on DRM && OF && I2C Please, make sure that it does NOT dependent on OF. ... > +obj-$(CONFIG_TINYDRM_SSD130X) += ssd130x.o I would keep the original name since we have I2C (fbdev) implementation, SPI and platform (fbtft), and now i2c (drm). I would like to avoid more confusion that we already have. -- With Best Regards, Andy Shevchenko