From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x
Date: Tue, 24 Jun 2014 15:51:53 +0100 [thread overview]
Message-ID: <20140624145153.GQ13803@lee--X1> (raw)
In-Reply-To: <4274516.nCpbjAuUJp@wuerfel>
On Tue, 24 Jun 2014, Arnd Bergmann wrote:
> On Tuesday 24 June 2014 13:46:34 Lee Jones wrote:
> > > > > > converting all addresses to to resources so drivers can easily pull
> > > > > > them out using platform_get_resource() and friends. Pushing the reg
> > > > >
> > > > > right. Can't we use of_address_to_resource here?
> > > >
> > > > We could, but that would be an extra layer. We'd be pulling the
> > > > address, putting it into a resource, then pulling it from the resource
> > > > for use. If we're going to be pulling addresses out manually, we're
> > > > probably better off using of_get_address(). But again, we're just
> > > > carrying out functionality which is already provided by the
> > > > framework.
> > >
> > > there is also of_ioremap().
> >
> > Isn't this SPARK only? And doesn't it require a populated resource?
> > Which is what I'm saying is the issue here i.e. we don't have one.
>
> Sorry, I meant of_iomap(). I think it's only for historic reaons
> that we have both. Probably of_iomap started out on powerpc with
> the same intention as the sparc of_ioremap.
>
> of_iomap does not require a resource, just an index.
Ah, this sounds like a better solution. I'll have a play, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>,
Sergei Shtylyov
<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x
Date: Tue, 24 Jun 2014 15:51:53 +0100 [thread overview]
Message-ID: <20140624145153.GQ13803@lee--X1> (raw)
In-Reply-To: <4274516.nCpbjAuUJp@wuerfel>
On Tue, 24 Jun 2014, Arnd Bergmann wrote:
> On Tuesday 24 June 2014 13:46:34 Lee Jones wrote:
> > > > > > converting all addresses to to resources so drivers can easily pull
> > > > > > them out using platform_get_resource() and friends. Pushing the reg
> > > > >
> > > > > right. Can't we use of_address_to_resource here?
> > > >
> > > > We could, but that would be an extra layer. We'd be pulling the
> > > > address, putting it into a resource, then pulling it from the resource
> > > > for use. If we're going to be pulling addresses out manually, we're
> > > > probably better off using of_get_address(). But again, we're just
> > > > carrying out functionality which is already provided by the
> > > > framework.
> > >
> > > there is also of_ioremap().
> >
> > Isn't this SPARK only? And doesn't it require a populated resource?
> > Which is what I'm saying is the issue here i.e. we don't have one.
>
> Sorry, I meant of_iomap(). I think it's only for historic reaons
> that we have both. Probably of_iomap started out on powerpc with
> the same intention as the sparc of_ioremap.
>
> of_iomap does not require a resource, just an index.
Ah, this sounds like a better solution. I'll have a play, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x
Date: Tue, 24 Jun 2014 15:51:53 +0100 [thread overview]
Message-ID: <20140624145153.GQ13803@lee--X1> (raw)
In-Reply-To: <4274516.nCpbjAuUJp@wuerfel>
On Tue, 24 Jun 2014, Arnd Bergmann wrote:
> On Tuesday 24 June 2014 13:46:34 Lee Jones wrote:
> > > > > > converting all addresses to to resources so drivers can easily pull
> > > > > > them out using platform_get_resource() and friends. Pushing the reg
> > > > >
> > > > > right. Can't we use of_address_to_resource here?
> > > >
> > > > We could, but that would be an extra layer. We'd be pulling the
> > > > address, putting it into a resource, then pulling it from the resource
> > > > for use. If we're going to be pulling addresses out manually, we're
> > > > probably better off using of_get_address(). But again, we're just
> > > > carrying out functionality which is already provided by the
> > > > framework.
> > >
> > > there is also of_ioremap().
> >
> > Isn't this SPARK only? And doesn't it require a populated resource?
> > Which is what I'm saying is the issue here i.e. we don't have one.
>
> Sorry, I meant of_iomap(). I think it's only for historic reaons
> that we have both. Probably of_iomap started out on powerpc with
> the same intention as the sparc of_ioremap.
>
> of_iomap does not require a resource, just an index.
Ah, this sounds like a better solution. I'll have a play, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-06-24 14:51 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 13:53 [RESEND 0/4] phy: Introduce support for MiPHY365x Lee Jones
2014-05-22 13:53 ` Lee Jones
2014-05-22 13:53 ` [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-05-22 13:53 ` Lee Jones
2014-06-10 11:00 ` Kishon Vijay Abraham I
2014-06-10 11:00 ` Kishon Vijay Abraham I
2014-06-17 11:23 ` Lee Jones
2014-06-17 11:23 ` Lee Jones
2014-06-18 9:50 ` Kishon Vijay Abraham I
2014-06-18 9:50 ` Kishon Vijay Abraham I
2014-06-18 9:50 ` Kishon Vijay Abraham I
2014-06-18 10:04 ` Lee Jones
2014-06-18 10:04 ` Lee Jones
2014-06-24 9:38 ` Arnd Bergmann
2014-06-24 9:38 ` Arnd Bergmann
2014-06-24 9:38 ` Arnd Bergmann
2014-06-24 12:46 ` Lee Jones
2014-06-24 12:46 ` Lee Jones
2014-06-24 14:08 ` Arnd Bergmann
2014-06-24 14:08 ` Arnd Bergmann
2014-06-24 14:08 ` Arnd Bergmann
2014-06-24 14:51 ` Lee Jones [this message]
2014-06-24 14:51 ` Lee Jones
2014-06-24 14:51 ` Lee Jones
2014-05-22 13:53 ` [PATCH 2/4] phy: miphy365x: Add MiPHY365x header file for DT x Driver defines Lee Jones
2014-05-22 13:53 ` Lee Jones
2014-06-25 20:53 ` Sergei Shtylyov
2014-06-25 20:53 ` Sergei Shtylyov
2014-05-22 13:53 ` [PATCH 3/4] ARM: DT: STi: Add DT node for MiPHY365x Lee Jones
2014-05-22 13:53 ` Lee Jones
2014-05-22 13:53 ` [PATCH 4/4] phy: miphy365x: Provide support for the MiPHY356x Generic PHY Lee Jones
2014-05-22 13:53 ` Lee Jones
2014-06-05 15:09 ` [RESEND 0/4] phy: Introduce support for MiPHY365x Lee Jones
2014-06-05 15:09 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2014-04-29 7:21 [PATCH " Lee Jones
2014-04-29 7:21 ` [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-04-29 7:21 ` Lee Jones
2014-05-19 13:56 ` Lee Jones
2014-05-19 13:56 ` Lee Jones
2014-05-19 14:00 ` Kishon Vijay Abraham I
2014-05-19 14:00 ` Kishon Vijay Abraham I
2014-05-19 14:07 ` Lee Jones
2014-05-19 14:07 ` Lee Jones
2014-03-12 13:14 [PATCH 0/4] phy: Introduce support for MiPHY365x Lee Jones
2014-03-12 13:14 ` [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-03-12 13:14 ` Lee Jones
2014-02-14 11:23 Lee Jones
2014-02-14 11:23 ` Lee Jones
2014-02-14 11:23 ` Lee Jones
2014-03-05 7:34 ` Mark Rutland
2014-03-05 7:34 ` Mark Rutland
2014-03-05 7:34 ` Mark Rutland
2014-03-05 8:40 ` Lee Jones
2014-03-05 8:40 ` Lee Jones
2014-03-05 8:40 ` Lee Jones
2014-03-05 9:12 ` Lee Jones
2014-03-05 9:12 ` Lee Jones
2014-03-05 9:12 ` Lee Jones
2014-02-12 16:03 Lee Jones
2014-02-12 16:03 ` Lee Jones
2014-02-12 16:40 ` Mark Rutland
2014-02-12 16:40 ` Mark Rutland
2014-02-12 16:40 ` Mark Rutland
2014-02-13 11:03 ` Lee Jones
2014-02-13 11:03 ` Lee Jones
2014-02-13 12:23 ` Mark Rutland
2014-02-13 12:23 ` Mark Rutland
2014-02-13 12:23 ` Mark Rutland
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=20140624145153.GQ13803@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.