linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
	linux-input@vger.kernel.org, pmeerw@pmeerw.net, jic23@kernel.org,
	linux-kernel@vger.kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	dmitry.torokhov@gmail.com, harald@ccbib.org,
	fabio.estevam@freescale.com, linux-iio@vger.kernel.org,
	marex@denx.de, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD
Date: Fri, 30 Sep 2016 00:14:30 +0100	[thread overview]
Message-ID: <20160929231430.GB13971@dell> (raw)
In-Reply-To: <1269746175.25077.ef1d8693-0ff3-4b50-a424-49eebba23da1.open-xchange@email.1und1.de>

On Thu, 29 Sep 2016, Stefan Wahren wrote:

> Hi Lee,
> 
> [add Rob and Mark]
> 
> > Lee Jones <lee.jones@linaro.org> hat am 29. September 2016 um 19:15
> > geschrieben:
> > 
> > 
> > On Thu, 29 Sep 2016, Stefan Wahren wrote:
> > > > Lee Jones <lee.jones@linaro.org> hat am 28. September 2016 um 03:05
> > > > geschrieben:
> > > > 
> > > > 
> > > > On Sat, 17 Sep 2016, Ksenija Stanojevic wrote:
> > > > 
> > > > > +
> > > > > +static int mxs_lradc_probe(struct platform_device *pdev)
> > > > > +{
> > > > > +	const struct of_device_id *of_id;
> > > > > +	struct device *dev = &pdev->dev;
> > > > > +	struct device_node *node = dev->of_node;
> > > > > +	struct mxs_lradc *lradc;
> > > > > +	struct mfd_cell *cells = NULL;
> > > > > +	int ret = 0;
> > > > > +	u32 ts_wires = 0;
> > > > > +
> > > > > +	lradc = devm_kzalloc(&pdev->dev, sizeof(*lradc), GFP_KERNEL);
> > > > > +	if (!lradc)
> > > > > +		return -ENOMEM;
> > > > > +
> > > > > +	of_id = of_match_device(mxs_lradc_dt_ids, &pdev->dev);
> > > > > +	lradc->soc = (enum mxs_lradc_id)of_id->data;
> > > > > +
> > > > > +	lradc->clk = devm_clk_get(&pdev->dev, NULL);
> > > > > +	if (IS_ERR(lradc->clk)) {
> > > > > +		dev_err(dev, "Failed to get the delay unit clock\n");
> > > > > +		return PTR_ERR(lradc->clk);
> > > > > +	}
> > > > > +
> > > > > +	ret = clk_prepare_enable(lradc->clk);
> > > > > +	if (ret) {
> > > > > +		dev_err(dev, "Failed to enable the delay unit clock\n");
> > > > > +		return ret;
> > > > > +	}
> > > > > +
> > > > > +	ret = of_property_read_u32(node, "fsl,lradc-touchscreen-wires",
> > > > 
> > > > Have you moved the documentation into devicetree/bindings/mfd?
> > > > 
> > > 
> > > i hope it's okay if i answer. The binding has moved to
> > > devicetree/binding/iio/adc/ [1]
> > > 
> > > Should it move completely to mfd or split too?
> > > 
> > > I'm asking myself how we keep DT ABI in the latter case.
> > > 
> > > [1] -
> > > http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/iio/adc/mxs-lradc.txt
> > 
> > I haven't read into the documentation too to deeply, but it stands to
> > reason that the bindings which are now being used in MFD should be
> > documented in the MFD binding document, and the ones which are no longer
> > used in the IIO driver should be removed.
> 
> sure, that isn't a problem.
> 
> The more interesting question would be: do we need a new compatible string for
> the mfd driver?

No, I don't think that is necessary.

> In that case the ADC won't probe for the combination of old devicetree blobs and
> new kernel.


-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2016-09-29 23:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 10:48 [PATCH v6 0/4] mxs-lradc: Split driver into MFD Ksenija Stanojevic
     [not found] ` <cover.1474108510.git.ksenija.stanojevic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-17 10:48   ` [PATCH v6 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD Ksenija Stanojevic
2016-09-28  1:05     ` Lee Jones
2016-09-29  1:38       ` Stefan Wahren
     [not found]         ` <1882238802.204734.75f5f595-10ac-4107-8738-e75dfde001f1.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-09-29 17:15           ` Lee Jones
2016-09-29 19:15             ` Stefan Wahren
2016-09-29 23:14               ` Lee Jones [this message]
2016-09-17 10:48   ` [PATCH v6 2/4] iio: adc: mxs-lradc: Add support for adc driver Ksenija Stanojevic
2016-09-17 10:48   ` [PATCH v6 3/4] input: touchscreen: mxs-lradc: Add support for touchscreen Ksenija Stanojevic
2016-09-17 10:48   ` [PATCH v6 4/4] iio: adc: mxs-lradc: Remove driver Ksenija Stanojevic
2016-09-19 19:59   ` [PATCH v6 0/4] mxs-lradc: Split driver into MFD Stefan Wahren

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=20160929231430.GB13971@dell \
    --to=lee.jones@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=fabio.estevam@freescale.com \
    --cc=harald@ccbib.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=ksenija.stanojevic@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=stefan.wahren@i2se.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).