mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Peter Mamonov <pmamonov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ata: intf_platform_ide: add OF bindings
Date: Fri, 04 Sep 2015 12:23:09 +0200	[thread overview]
Message-ID: <1441362189.7971.12.camel@pengutronix.de> (raw)
In-Reply-To: <20150904124022.093ec9a7@berta>

Am Freitag, den 04.09.2015, 12:40 +0300 schrieb Peter Mamonov:
> Hi, Lucas!
> 
> On Thu, 03 Sep 2015 17:46:32 +0200
> Lucas Stach <l.stach@pengutronix.de> wrote:
> 
> > Hi Peter.
> > 
> > Sorry, but this patch is wrong. You can't just make up completely
> > ad-hoc DT bindings. You are pushing platformdata 1:1 into the DT,
> > which is not how the conversion to DT should be done.
> 
> Could you clarify your point? My current understanding is that drivers
> instantiation from a platform code and from a DT are equal approaches,
> which should mirror each other.
> 
No not at all. DT bindings are API between the DT and barebox/Linux, so
they can not in all cases mirror platformdata, which we are able to
change at will.

DT instantiation need a well thought through binding, which isn't some
ad-hoc mirroring of the current platformdata.

Normally the binding is established by writing it down in the Linux
kernel Documentation/devicetree/bindings folder (and obviously getting
it through the DT review process).

> > 
> > There is also no pre-existing binding for "ata-generic" in the Linux
> > kernel which would define any of those properties.
> > 
> > Most likely your IDE controller is inside some SoC specific block,
> > with a specific compatible, which may also handle clocks and other
> > required stuff and that one should instantiate the IDE driver if
> > needed.
> 
> I've got your point. However, drivers/ata/pata_of_platform.c from Linux
> also lacks any clock/stuff initialization.
> 
If there is already a Linux driver with this binding you can reuse that
one, as it's already established, even if there is no proper
documentation there. If the binding is enough for your use-case that's
okay.

You can however not make any ad-hoc additions to the established
bindings, so if it doesn't fit your needs you need to propose the
addition to the generic binding to DT reviewers, or think about a SoC
specific binding if you need clocks/regulators or other things that
don't belong in a generic binding.

Regards,
Lucas

> Regards,
> Peter
> 
> 
> > 
> > Regards,
> > Lucas
> > 
> > Am Donnerstag, den 03.09.2015, 16:38 +0300 schrieb Peter Mamonov:
> > > Signed-off-by: Peter Mamonov <pmamonov@gmail.com>
> > > ---
> > >  drivers/ata/intf_platform_ide.c | 35
> > > +++++++++++++++++++++++++++++++++-- 1 file changed, 33
> > > insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/ata/intf_platform_ide.c
> > > b/drivers/ata/intf_platform_ide.c index 0d392d8..f20e0e0 100644
> > > --- a/drivers/ata/intf_platform_ide.c
> > > +++ b/drivers/ata/intf_platform_ide.c
> > > @@ -29,6 +29,7 @@
> > >  #include <ata_drive.h>
> > >  #include <platform_ide.h>
> > >  #include <linux/err.h>
> > > +#include <of.h>
> > >  
> > >  /**
> > >   * Setup the register specific addresses for an ATA like divice
> > > @@ -85,10 +86,31 @@ static int platform_ide_probe(struct device_d
> > > *dev) void *reg_base, *alt_base = NULL;
> > >  	struct resource *reg, *alt;
> > >  	int mmio = 0;
> > > +	struct device_node *dn = dev->device_node;
> > > +	u32 tmp32;
> > >  
> > >  	if (pdata == NULL) {
> > > -		dev_err(dev, "No platform data. Cannot
> > > continue\n");
> > > -		return -EINVAL;
> > > +		/* try to get platform data from the device tree */
> > > +		if (dn == NULL) {
> > > +			dev_err(dev, "No platform data. Cannot
> > > continue\n");
> > > +			return -EINVAL;
> > > +		}
> > > +
> > > +		pdata = xzalloc(sizeof(struct ide_port_info));
> > > +
> > > +		if (!pdata) {
> > > +			dev_err(dev, "Platform data allocation
> > > failed\n");
> > > +			return -ENOMEM;
> > > +		}
> > > +		device_add_data(dev, pdata, sizeof(struct
> > > ide_port_info)); +
> > > +		if (of_property_read_bool(dn, "dataif-be"))
> > > +			pdata->dataif_be = 1;
> > > +
> > > +		if (of_property_read_u32(dn, "reg-shift", &tmp32)
> > > == 0)
> > > +			pdata->ioport_shift = (unsigned)tmp32;
> > > +
> > > +		dev->platform_data = pdata;
> > >  	}
> > >  
> > >  	reg_base = dev_request_mem_region(dev, 0);
> > > @@ -136,9 +158,18 @@ static int platform_ide_probe(struct device_d
> > > *dev) return rc;
> > >  }
> > >  
> > > +static __maybe_unused struct of_device_id platform_ide_dt_ids[] = {
> > > +	{
> > > +		.compatible = "ata-generic",
> > > +	}, {
> > > +		/* sentinel */
> > > +	}
> > > +};
> > > +
> > >  static struct driver_d platform_ide_driver = {
> > >  	.name   = "ide_intf",
> > >  	.probe  = platform_ide_probe,
> > > +	.of_compatible = DRV_OF_COMPAT(platform_ide_dt_ids),
> > >  };
> > >  device_platform_driver(platform_ide_driver);
> > >  
> > 
> 

-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-09-04 10:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 13:38 Peter Mamonov
2015-09-03 14:24 ` Antony Pavlov
2015-09-03 15:33   ` Peter Mamonov
2015-09-03 16:04   ` Peter Mamonov
2015-09-03 18:13     ` Sascha Hauer
2015-09-07 15:44       ` [PATCHv2] " Peter Mamonov
2015-09-07 15:53         ` Lucas Stach
2015-09-07 16:43           ` [PATCHv3] " Peter Mamonov
2015-09-09  6:54             ` Sascha Hauer
2015-09-03 15:46 ` [PATCH] " Lucas Stach
2015-09-03 16:31   ` Antony Pavlov
2015-09-03 18:16     ` Sascha Hauer
2015-09-04 10:15       ` Peter Mamonov
2015-09-04  9:40   ` Peter Mamonov
2015-09-04 10:23     ` Lucas Stach [this message]

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=1441362189.7971.12.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=pmamonov@gmail.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