Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1590598 > unrolled thread

Re: [PATCH] regulator: hi655x: Add DT bindings so module autoloads

Started byMark Brown <broonie@kernel.org>
First post2017-03-01 20:50 +0100
Last post2017-03-01 20:50 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] regulator: hi655x: Add DT bindings so module autoloads Mark Brown <broonie@kernel.org> - 2017-03-01 20:50 +0100

#1590598 — Re: [PATCH] regulator: hi655x: Add DT bindings so module autoloads

FromMark Brown <broonie@kernel.org>
Date2017-03-01 20:50 +0100
SubjectRe: [PATCH] regulator: hi655x: Add DT bindings so module autoloads
Message-ID<tgfBT-5HN-13@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On Tue, Feb 28, 2017 at 07:07:06PM -0600, Jeremy Linton wrote:
> The hi655x driver is required for mmc/sd functionality on the
> 96boards hikey, and likely other platforms. When built as
> a standalone module it doesn't get automatically loaded because
> it is missing the module probe hooks.

> +static const struct of_device_id hi655x_dt_ids[] = {
> +	{ .compatible = "hisilicon,hi655x-pmic",  },
> +	{},
> +};
> +MODULE_DEVICE_TABLE(of, hi655x_dt_ids);

This is an MFD subdevice, I'd expect it to instantiate as a platform
device from the MFD - there shouldn't be a compatible string in the DT
and indeed one is not documented (I see something slipped into the
example but it's not in the actual binding).  It's not like this device
can exist independently of the parent device and that compatible string
is not specific enough anyway.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web