linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Alan Stern <stern@rowland.harvard.edu>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Helge Deller <deller@gmx.de>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Janusz Krzysztofik <jmkrzyszt@gmail.com>
Subject: [RFC RFT PATCH 0/4] ARM: OMAP1: clock: Convert to CCF
Date: Fri, 11 Mar 2022 00:33:03 +0100	[thread overview]
Message-ID: <20220310233307.99220-1-jmkrzyszt@gmail.com> (raw)

The main motivation behind this series is planned resurection of OMAP1
camera driver.  Since OMAP1 clock internals have never been visible to
drivers, that driver used to use v4l2-clk to expose a pixel clock for a
sensor.  The v4l2-clk code has been recently depreciated and removed from
the media subtree, hence the need for an alternative solution.

Janusz Krzysztofik (4):
  ARM: OMAP1: clock: Remove unused code
  ARM: OMAP1: clock: Remove noop code
  ARM: OMAP1: Prepare for conversion of OMAP1 clocks to CCF
  ARM: OMAP1: clock: Convert to CCF

 arch/arm/Kconfig                 |   2 +-
 arch/arm/mach-omap1/clock.c      | 791 ++++++++++++-------------------
 arch/arm/mach-omap1/clock.h      | 191 ++------
 arch/arm/mach-omap1/clock_data.c | 491 ++++++++-----------
 arch/arm/mach-omap1/io.c         |   5 -
 arch/arm/mach-omap1/mcbsp.c      |   8 +-
 arch/arm/mach-omap1/ocpi.c       |   4 +-
 arch/arm/mach-omap1/serial.c     |   6 +-
 arch/arm/mach-omap1/time.c       |   5 +
 arch/arm/mach-omap1/timer32k.c   |   2 +-
 drivers/usb/host/ohci-omap.c     |   8 +-
 drivers/video/fbdev/omap/lcdc.c  |   6 +-
 12 files changed, 582 insertions(+), 937 deletions(-)

The series has been tested on OMAP1510 based Amstrad Delta board,
where it works best on top of two recently submitted fixes:
ARM: OMAP1: clock: Fix early UART rate issues
ARM: OMAP1: clock: Fix UART rate reporting algorithm

-- 
2.35.1


             reply	other threads:[~2022-03-10 23:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 23:33 Janusz Krzysztofik [this message]
2022-03-10 23:33 ` [RFC PATCH 1/4] ARM: OMAP1: clock: Remove unused code Janusz Krzysztofik
2022-03-10 23:33 ` [RFC PATCH 2/4] ARM: OMAP1: clock: Remove noop code Janusz Krzysztofik
2022-03-21 21:54   ` [PATCH v2] ARM: OMAP1: Prepare for conversion of OMAP1 clocks to CCF Janusz Krzysztofik
2022-03-22 12:02     ` Mark Brown
2022-03-22 16:36     ` Aaro Koskinen
2022-03-22 19:07       ` Aaro Koskinen
2022-03-26 21:17         ` Janusz Krzysztofik
2022-04-06 13:21           ` Aaro Koskinen
2022-04-06 18:48             ` Janusz Krzysztofik
2022-04-06 20:00               ` Aaro Koskinen
2022-03-31  9:19     ` Ulf Hansson
2022-03-31 18:29       ` Janusz Krzysztofik
2022-03-10 23:33 ` [RFC PATCH 3/4] " Janusz Krzysztofik
2022-03-10 23:33 ` [RFC RFT PATCH 4/4] ARM: OMAP1: clock: Convert " Janusz Krzysztofik
2022-03-12  8:14 ` [RFC RFT PATCH 0/4] " Tony Lindgren
2022-03-19 18:49   ` Aaro Koskinen
2022-03-19 21:21     ` Aaro Koskinen
2022-03-20  0:15       ` Janusz Krzysztofik
2022-03-21  8:01   ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220310233307.99220-1-jmkrzyszt@gmail.com \
    --to=jmkrzyszt@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=deller@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).