Hi Arnd,
Sorry for late reply.
On Friday 12 December 2014 05:01 PM, Arnd Bergmann wrote:
On Friday 12 December 2014 13:15:43 Pankaj Dubey wrote:
+
+static void __iomem *exynos_chipid_base;
+
+struct exynos_chipid_info exynos_soc_info;
+EXPORT_SYMBOL(exynos_soc_info);
The soc_device already h
On Fri, Dec 12, 2014 at 1:45 AM, Pankaj Dubey wrote:
> Hi Rob,
>
> On Thursday 11 December 2014 11:00 PM, Rob Herring wrote:
>>
>> On Thu, Dec 11, 2014 at 2:07 AM, Pankaj Dubey
>> wrote:
>>>
>>> Exynos SoCs have Chipid, for identification of product IDs
>>> and SoC revisions. This patch intendes
On Friday 12 December 2014 13:15:43 Pankaj Dubey wrote:
> >> +
> >> +static void __iomem *exynos_chipid_base;
> >> +
> >> +struct exynos_chipid_info exynos_soc_info;
> >> +EXPORT_SYMBOL(exynos_soc_info);
> >
> > The soc_device already has similar data.Why is this needed? Is it
> > temporary for com
Hi Rob,
On Thursday 11 December 2014 11:00 PM, Rob Herring wrote:
On Thu, Dec 11, 2014 at 2:07 AM, Pankaj Dubey wrote:
Exynos SoCs have Chipid, for identification of product IDs
and SoC revisions. This patch intendes to provide initialization
code for all these functionalites.
This driver use
On Thu, Dec 11, 2014 at 2:07 AM, Pankaj Dubey wrote:
> Exynos SoCs have Chipid, for identification of product IDs
> and SoC revisions. This patch intendes to provide initialization
> code for all these functionalites.
>
> This driver usese existing binding for exnos-chipid.
s/usese/uses/
s/exnos/
Exynos SoCs have Chipid, for identification of product IDs
and SoC revisions. This patch intendes to provide initialization
code for all these functionalites.
This driver usese existing binding for exnos-chipid.
CC: Grant Likely
CC: Rob Herring
CC: Linus Walleij
Signed-off-by: Pankaj Dubey
--
6 matches
Mail list logo