All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,
	Koen Kooi <koen@dominion.thruhere.net>,
	Matt Porter <mporter@ti.com>, Russ Dill <Russ.Dill@ti.com>,
	linux-omap@vger.kernel.org
Subject: Re: [RFC 2/7] capebus: Add beaglebone board support
Date: Tue, 30 Oct 2012 16:57:15 -0700	[thread overview]
Message-ID: <20121030235714.GB12739@atomide.com> (raw)
In-Reply-To: <DE47929E-9579-4DD2-B01C-08554D49FADE@antoniou-consulting.com>

* Pantelis Antoniou <panto@antoniou-consulting.com> [121030 13:18]:
> On Oct 30, 2012, at 9:39 PM, Tony Lindgren wrote:
> 
> > * Pantelis Antoniou <panto@antoniou-consulting.com> [121030 12:00]:
> >> +
> >> +	priv->lcdc_oh = omap_hwmod_lookup("lcdc");
> >> +	if (priv->lcdc_oh == NULL) {
> >> +		dev_err(&pdev->dev, "Failed to lookup omap_hwmod lcdc\n");
> >> +		return -ENODEV;
> >> +	}
> >> +
> >> +	priv->lcdc_pdev = omap_device_build("da8xx_lcdc", 0, priv->lcdc_oh,
> >> +			&priv->lcd_pdata,
> >> +			sizeof(struct da8xx_lcdc_platform_data),
> >> +			NULL, 0, 0);
> >> +	if (priv->lcdc_pdev == NULL) {
> >> +		dev_err(&pdev->dev, "Failed to build LCDC device\n");
> >> +		return -ENODEV;
> >> +	}
> > 
> > ..and these kind of things need to become private to
> > arch/arm/mach-omap2, we already have it working for other
> > devices with device tree.
> > 
> > Regards,
> > 
> > Tony
> 
> I see,
> 
> I know that if the device driver is DTified it will pick up the hwmod automatically.
> The issue is that the driver is question is not yet; how would I go about
> creating the platform device and having it pick up the hwmod automatically?

Maybe you should make this DT only driver for omap? We already
have am33xx DT only to start with.

If you really need the platform device still, just take a look
at the many platform device creating files under arch/arm/mach-omap2.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/7] capebus: Add beaglebone board support
Date: Tue, 30 Oct 2012 16:57:15 -0700	[thread overview]
Message-ID: <20121030235714.GB12739@atomide.com> (raw)
In-Reply-To: <DE47929E-9579-4DD2-B01C-08554D49FADE@antoniou-consulting.com>

* Pantelis Antoniou <panto@antoniou-consulting.com> [121030 13:18]:
> On Oct 30, 2012, at 9:39 PM, Tony Lindgren wrote:
> 
> > * Pantelis Antoniou <panto@antoniou-consulting.com> [121030 12:00]:
> >> +
> >> +	priv->lcdc_oh = omap_hwmod_lookup("lcdc");
> >> +	if (priv->lcdc_oh == NULL) {
> >> +		dev_err(&pdev->dev, "Failed to lookup omap_hwmod lcdc\n");
> >> +		return -ENODEV;
> >> +	}
> >> +
> >> +	priv->lcdc_pdev = omap_device_build("da8xx_lcdc", 0, priv->lcdc_oh,
> >> +			&priv->lcd_pdata,
> >> +			sizeof(struct da8xx_lcdc_platform_data),
> >> +			NULL, 0, 0);
> >> +	if (priv->lcdc_pdev == NULL) {
> >> +		dev_err(&pdev->dev, "Failed to build LCDC device\n");
> >> +		return -ENODEV;
> >> +	}
> > 
> > ..and these kind of things need to become private to
> > arch/arm/mach-omap2, we already have it working for other
> > devices with device tree.
> > 
> > Regards,
> > 
> > Tony
> 
> I see,
> 
> I know that if the device driver is DTified it will pick up the hwmod automatically.
> The issue is that the driver is question is not yet; how would I go about
> creating the platform device and having it pick up the hwmod automatically?

Maybe you should make this DT only driver for omap? We already
have am33xx DT only to start with.

If you really need the platform device still, just take a look
at the many platform device creating files under arch/arm/mach-omap2.

Regards,

Tony

  reply	other threads:[~2012-10-30 23:57 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 16:52 [RFC 0/7] Capebus; a bus for SoCs using simple expansion connectors Pantelis Antoniou
2012-10-31 16:52 ` Pantelis Antoniou
2012-10-31 16:52 ` [RFC 1/7] capebus: Core capebus support Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-31 21:55   ` Russ Dill
2012-10-31 21:55     ` Russ Dill
2012-10-31 22:07     ` Pantelis Antoniou
2012-10-31 22:07       ` Pantelis Antoniou
2012-11-01  0:55       ` Russ Dill
2012-11-01  0:55         ` Russ Dill
2012-10-31 16:52 ` [RFC 2/7] capebus: Add beaglebone board support Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-30 19:36   ` Tony Lindgren
2012-10-30 19:36     ` Tony Lindgren
2012-10-30 19:39   ` Tony Lindgren
2012-10-30 19:39     ` Tony Lindgren
2012-10-30 20:16     ` Pantelis Antoniou
2012-10-30 20:16       ` Pantelis Antoniou
2012-10-30 23:57       ` Tony Lindgren [this message]
2012-10-30 23:57         ` Tony Lindgren
2012-10-31 16:52 ` [RFC 3/7] capebus: Beaglebone generic cape support Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-31 16:52 ` [RFC 4/7] capebus: Beaglebone geiger " Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-31 16:52 ` [RFC 5/7] capebus: Beaglebone capebus DT update Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-31 16:52 ` [RFC 6/7] capebus: Document DT bindings Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-31 16:52 ` [RFC 7/7] capebus: Documentation; capebus-summary Pantelis Antoniou
2012-10-31 16:52   ` Pantelis Antoniou
2012-10-31 21:56 ` [RFC 0/7] Capebus; a bus for SoCs using simple expansion connectors Russ Dill
2012-10-31 21:56   ` Russ Dill
2012-10-31 22:03   ` Pantelis Antoniou
2012-10-31 22:03     ` Pantelis Antoniou

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=20121030235714.GB12739@atomide.com \
    --to=tony@atomide.com \
    --cc=Russ.Dill@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mporter@ti.com \
    --cc=panto@antoniou-consulting.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.