All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Dan Murphy <dmurphy@ti.com>,
	linux-omap@vger.kernel.org, tony@atomide.com,
	devicetree@vger.kernel.org, t-kristo@ti.com, s-anna@ti.com,
	p.zabel@pengutronix.de
Subject: Re: [RFC 01/11] drivers: reset: TI: SoC reset controller support.
Date: Tue, 29 Apr 2014 22:36:33 +0200	[thread overview]
Message-ID: <6639369.9mIUuXImgB@wuerfel> (raw)
In-Reply-To: <1398802790-29287-2-git-send-email-dmurphy@ti.com>

On Tuesday 29 April 2014 15:19:40 Dan Murphy wrote:
> +#ifndef _RESET_TI_H_
> +#define _RESET_TI_H_
> +
> +#ifdef CONFIG_RESET_TI
> +void ti_dt_reset_init(void);
> +#else
> +static inline void ti_dt_reset_init(void){ return; };
> +#endif

Why can't this be a regular platform device driver that gets
initialized through an initcall rather than get called from
platform code?

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 01/11] drivers: reset: TI: SoC reset controller support.
Date: Tue, 29 Apr 2014 22:36:33 +0200	[thread overview]
Message-ID: <6639369.9mIUuXImgB@wuerfel> (raw)
In-Reply-To: <1398802790-29287-2-git-send-email-dmurphy@ti.com>

On Tuesday 29 April 2014 15:19:40 Dan Murphy wrote:
> +#ifndef _RESET_TI_H_
> +#define _RESET_TI_H_
> +
> +#ifdef CONFIG_RESET_TI
> +void ti_dt_reset_init(void);
> +#else
> +static inline void ti_dt_reset_init(void){ return; };
> +#endif

Why can't this be a regular platform device driver that gets
initialized through an initcall rather than get called from
platform code?

	Arnd

  reply	other threads:[~2014-04-29 20:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 20:19 [RFC] TI Reset Driver adapted to the reset core Dan Murphy
2014-04-29 20:19 ` Dan Murphy
2014-04-29 20:19 ` [RFC 01/11] drivers: reset: TI: SoC reset controller support Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:36   ` Arnd Bergmann [this message]
2014-04-29 20:36     ` Arnd Bergmann
2014-04-30  8:20   ` Philipp Zabel
2014-04-30  8:20     ` Philipp Zabel
2014-04-30 17:50     ` Dan Murphy
2014-04-30 17:50       ` Dan Murphy
2014-04-29 20:19 ` [RFC 02/11] drivers: reset: dra7: Add reset data for dra7xx Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 03/11] drivers: reset: omap5: Add reset data for omap5 Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 04/11] drivers: reset: am335: Add reset data for am335 Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 05/11] drivers: reset: am43xx: Add reset data for am43xx Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 06/11] ARM: OMAP: Add reset init to prcm file Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 07/11] ARM: TI: Describe the ti reset DT entries Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 08/11] ARM: dts: am33xx: Add prcm_resets node Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:34   ` Arnd Bergmann
2014-04-29 20:34     ` Arnd Bergmann
2014-04-30  0:22     ` Tony Lindgren
2014-04-30  0:22       ` Tony Lindgren
2014-04-30 18:00       ` Dan Murphy
2014-04-30 18:00         ` Dan Murphy
2014-04-30 18:10         ` Tony Lindgren
2014-04-30 18:10           ` Tony Lindgren
2014-04-30 18:13           ` Dan Murphy
2014-04-30 18:13             ` Dan Murphy
2014-04-30 22:33             ` Tony Lindgren
2014-04-30 22:33               ` Tony Lindgren
2014-05-01 18:46               ` Dan Murphy
2014-05-01 18:46                 ` Dan Murphy
2014-04-29 20:19 ` [RFC 09/11] ARM: dts: am4372: " Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 10/11] ARM: dts: dra7: Add prm_resets node Dan Murphy
2014-04-29 20:19   ` Dan Murphy
2014-04-29 20:19 ` [RFC 11/11] ARM: dts: omap5: " Dan Murphy
2014-04-29 20:19   ` Dan Murphy

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=6639369.9mIUuXImgB@wuerfel \
    --to=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=s-anna@ti.com \
    --cc=t-kristo@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.