mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: David Lechner <david@lechnology.com>,
	<linux-arm-kernel@lists.infradead.org>
Cc: Kevin Hilman <khilman@kernel.org>,
	Lee Jones <lee.jones@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Adam Ford <aford173@gmail.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] ARM: davinci: common clock prep work
Date: Mon, 22 Jan 2018 16:43:55 +0530	[thread overview]
Message-ID: <28bb9f44-c6b5-e2e9-2d13-5b50dbceac7b@ti.com> (raw)
In-Reply-To: <1516418424-28686-1-git-send-email-david@lechnology.com>

On Saturday 20 January 2018 08:50 AM, David Lechner wrote:
> This series contains some changes needed for the conversion of arch/arm/mach-
> davinci to the common clock framework.
> 
> Most of the boards in mach-davinci do not have device tree support. However,
> CFGCHIP, which is a syscon regmap, is needed during clock init in early boot.
> Using a platform device for the syscon at this point is not an option. So,
> this series introduces a new way to register a syscon regmap on non-DT systems.
> 
> The DA8XX USB PHY driver is a consumer of the CFGCHIP syscon regmap, so some
> changes are needed in that driver as well since we are removing the syscon
> platform devices. The patch "phy: da8xx-usb: rename clock con_ids" doesn't
> have anything to do with syscon, but I included in this series because we are
> touching PHY code here anyway and it is also a dependency for the upcoming
> common clock framework conversion changes.
> 
> Maintainers, please coordinate with Sekhar before committing. We will probably
> want everything to go through the linux-davinci tree if possible.

You should wait for some more feedback before resending anything, but I
think it will be easier to reivew/accept this if the changes are just
related to removal of "syscon" platform device from devices-da8xx.c.

It _seems_ like this series does more than just that, and I hope it can
be pared down.

Thanks,
Sekhar

  parent reply	other threads:[~2018-01-22 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20  3:20 David Lechner
2018-01-20  3:20 ` [PATCH 1/6] mfd: syscon: Add syscon_register() function David Lechner
2018-01-22 10:53   ` Sekhar Nori
2018-01-22 11:08     ` Arnd Bergmann
2018-01-22 11:39       ` Sekhar Nori
2018-01-22 16:47         ` David Lechner
2018-01-20  3:20 ` [PATCH 2/6] phy: da8xx-usb: Always check for syscon compatible David Lechner
2018-01-20  3:20 ` [PATCH 3/6] phy: da8xx-usb: rename clock con_ids David Lechner
2018-01-20  3:20 ` [PATCH 4/6] ARM: davinci: move davinci_clk_init() to init_time David Lechner
2018-01-23 12:02   ` Sekhar Nori
2018-01-20  3:20 ` [PATCH 5/6] ARM: da8xx: Move CFGCHIP registration " David Lechner
2018-01-20  3:20 ` [PATCH 6/6] phy: da8xx-usb: drop use of syscon_regmap_lookup_by_pdevname() David Lechner
2018-01-22 11:13 ` Sekhar Nori [this message]
2018-01-23 23:40   ` [PATCH 0/6] ARM: davinci: common clock prep work David Lechner

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=28bb9f44-c6b5-e2e9-2d13-5b50dbceac7b@ti.com \
    --to=nsekhar@ti.com \
    --cc=aford173@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bgolaszewski@baylibre.com \
    --cc=david@lechnology.com \
    --cc=khilman@kernel.org \
    --cc=kishon@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome