public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] dm: add dev_get_reg() for getting device node's reg
Date: Wed, 16 Dec 2015 11:53:50 -0700	[thread overview]
Message-ID: <5671B33E.5070701@wwwdotorg.org> (raw)
In-Reply-To: <1450197123-1822-1-git-send-email-p.marczak@samsung.com>

On 12/15/2015 09:32 AM, Przemyslaw Marczak wrote:
> commit: dm: core: Enable optional use of fdt_translate_address()
>
> enables device's bus/child address translation method, depending
> on bus 'ranges' property and including child 'reg' property.
> This change makes impossible to decode the 'reg' for node with
> '#size-cells' equal to 0.
>
> Such case is possible by the specification and is also used in U-Boot,
> e.g. by I2C uclass or S5P GPIO - the last one is broken at present.

Can you please explain the problem you're seeing in more detail? Without 
any context, my initial reaction is that this is simply a bug somewhere. 
That bug should be fixed, rather than introducing new APIs to hide the 
problem.

> For this purpose this patch set introduces new core function:
>   fdt_addr_t dev_get_reg(struct udevice *dev)
> which returns the 'reg' value in the same way as previously dev_get_addr().
>
> This fixes s5p gpio driver and booting issue on few Exynos based boards:
> - Trats2
> - Odroid U3/X2

Looking at arch/arm/dts/exynos4412-trats2.dts, I see the following:


        i2c at 138d0000 {
                 samsung,i2c-sda-delay = <100>;
                 samsung,i2c-slave-addr = <0x10>;
                 samsung,i2c-max-bus-freq = <100000>;
                 status = "okay";

                 max77686_pmic at 09 {
                         compatible = "maxim,max77686";
                         interrupts = <7 0>;
                         reg = <0x09 0 0>;

Is that the node you're having problems with? If so, I believe this may 
simply be due to invalid DT content. In exynos4.dtsi, that i2c node is 
defined as:

         i2c at 138d0000 {
                 #address-cells = <1>;
                 #size-cells = <0>;

Thus, any reg property in a child of that node must only contain a 
single cell (the sum of #address-cells and #size-cells in the parent). 
Does fixing the DT so it's valid solve your issue at all?

  parent reply	other threads:[~2015-12-16 18:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 16:32 [U-Boot] [PATCH 0/3] dm: add dev_get_reg() for getting device node's reg Przemyslaw Marczak
2015-12-15 16:32 ` [U-Boot] [PATCH 1/3] dm: core: extend API by new function: dev_get_reg() Przemyslaw Marczak
2015-12-15 16:32 ` [U-Boot] [PATCH 2/3] gpio: s5p: use dev_get_reg() instead of dev_get_addr() Przemyslaw Marczak
2015-12-15 16:32 ` [U-Boot] [PATCH 3/3] dm: i2c: get chip address with dev_get_reg() Przemyslaw Marczak
2015-12-16 18:53 ` Stephen Warren [this message]
2015-12-16 19:07   ` [U-Boot] [PATCH 0/3] dm: add dev_get_reg() for getting device node's reg Stephen Warren
2015-12-29  8:47     ` Przemyslaw Marczak
2016-01-04 20:06       ` Stephen Warren
2016-01-05 15:38         ` Przemyslaw Marczak
2016-01-05 17:12           ` Stephen Warren
2016-01-06  0:24             ` Simon Glass
2016-01-06 19:14               ` Stephen Warren
2016-01-07 11:57               ` Przemyslaw Marczak
2015-12-29  8:47   ` Przemyslaw Marczak
2016-01-04 20:02     ` Stephen Warren
2016-01-05  0:58       ` Simon Glass
2016-01-05 17:05         ` Stephen Warren
2016-01-05 15:37       ` Przemyslaw Marczak
2016-01-05 17:08         ` Stephen Warren
2016-01-07 11:45           ` Przemyslaw Marczak

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=5671B33E.5070701@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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