On 06/10/2016 01:18, Benjamin Herrenschmidt wrote:
On Tue, 2016-10-04 at 13:02 +0100, John Garry wrote:
Right, so I think Zhichang can make the necessary generic changes to
8250 OF driver to support IO port as well as MMIO-based.
However an LPC-based earlycon driver is still required.
A note
On 06/10/2016 01:18, Benjamin Herrenschmidt wrote:
On Tue, 2016-10-04 at 13:02 +0100, John Garry wrote:
Right, so I think Zhichang can make the necessary generic changes to
8250 OF driver to support IO port as well as MMIO-based.
However an LPC-based earlycon driver is still required.
A note
On Tue, 2016-10-04 at 13:02 +0100, John Garry wrote:
> Right, so I think Zhichang can make the necessary generic changes to
> 8250 OF driver to support IO port as well as MMIO-based.
>
> However an LPC-based earlycon driver is still required.
>
> A note on hip07-based D05 (for those unaware):
On Tue, 2016-10-04 at 13:02 +0100, John Garry wrote:
> Right, so I think Zhichang can make the necessary generic changes to
> 8250 OF driver to support IO port as well as MMIO-based.
>
> However an LPC-based earlycon driver is still required.
>
> A note on hip07-based D05 (for those unaware):
On 02/10/2016 23:03, Jon Masters wrote:
On 09/14/2016 02:32 PM, Arnd Bergmann wrote:
On Wednesday, September 14, 2016 10:50:44 PM CEST zhichang.yuan wrote:
And there are probably multiple child devices under LPC, the global
arm64_extio_ops only can cover one PIO range. It is fortunate only
On 02/10/2016 23:03, Jon Masters wrote:
On 09/14/2016 02:32 PM, Arnd Bergmann wrote:
On Wednesday, September 14, 2016 10:50:44 PM CEST zhichang.yuan wrote:
And there are probably multiple child devices under LPC, the global
arm64_extio_ops only can cover one PIO range. It is fortunate only
On 09/14/2016 02:32 PM, Arnd Bergmann wrote:
> On Wednesday, September 14, 2016 10:50:44 PM CEST zhichang.yuan wrote:
>> And there are probably multiple child devices under LPC, the global
>> arm64_extio_ops only can cover one PIO range. It is fortunate only ipmi
>> driver can not support I/O
On 09/14/2016 02:32 PM, Arnd Bergmann wrote:
> On Wednesday, September 14, 2016 10:50:44 PM CEST zhichang.yuan wrote:
>> And there are probably multiple child devices under LPC, the global
>> arm64_extio_ops only can cover one PIO range. It is fortunate only ipmi
>> driver can not support I/O
rg; John Garry;
> > > will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> > > Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> > > b...@kernel.crashing.org; zourongr...@gmail.com;
> liviu.du...@arm.com;
> > > kant...@163.com
> > > Subject: Re
rg; John Garry;
> > > will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> > > Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> > > b...@kernel.crashing.org; zourongr...@gmail.com;
> liviu.du...@arm.com;
> > > kant...@163.com
> > > Subject: Re
On Saturday, September 24, 2016 4:14:15 PM CEST zhichang wrote:
>
> In V3, the outb is :
>
> void outb(u8 value, unsigned long addr)
> {
> if (!arm64_extio_ops || arm64_extio_ops->start > addr ||
> arm64_extio_ops->end < addr)
> writeb(value,
On Saturday, September 24, 2016 4:14:15 PM CEST zhichang wrote:
>
> In V3, the outb is :
>
> void outb(u8 value, unsigned long addr)
> {
> if (!arm64_extio_ops || arm64_extio_ops->start > addr ||
> arm64_extio_ops->end < addr)
> writeb(value,
Hi, Arnd,
On 2016年09月23日 23:55, Arnd Bergmann wrote:
> On Friday, September 23, 2016 2:59:55 PM CEST Gabriele Paoloni wrote:
>>
From the perspective of the indirect IO function the input parameter
is an unsigned long addr that (now) can be either:
1) an IO token coming from a
Hi, Arnd,
On 2016年09月23日 23:55, Arnd Bergmann wrote:
> On Friday, September 23, 2016 2:59:55 PM CEST Gabriele Paoloni wrote:
>>
From the perspective of the indirect IO function the input parameter
is an unsigned long addr that (now) can be either:
1) an IO token coming from a
Hi, Arnd,
On 2016年09月23日 17:51, Arnd Bergmann wrote:
> On Friday, September 23, 2016 12:27:17 AM CEST zhichang.yuan wrote:
>> For this patch sketch, I have a question.
>> Do we call pci_address_to_pio in arch_of_address_to_pio to get the
>> corresponding logical IO port
>> for LPC??
>
>
> No,
Hi, Arnd,
On 2016年09月23日 17:51, Arnd Bergmann wrote:
> On Friday, September 23, 2016 12:27:17 AM CEST zhichang.yuan wrote:
>> For this patch sketch, I have a question.
>> Do we call pci_address_to_pio in arch_of_address_to_pio to get the
>> corresponding logical IO port
>> for LPC??
>
>
> No,
On Friday, September 23, 2016 2:59:55 PM CEST Gabriele Paoloni wrote:
>
> > > From the perspective of the indirect IO function the input parameter
> > > is an unsigned long addr that (now) can be either:
> > > 1) an IO token coming from a legacy pci device
> > > 2) a phys address that lives on
On Friday, September 23, 2016 2:59:55 PM CEST Gabriele Paoloni wrote:
>
> > > From the perspective of the indirect IO function the input parameter
> > > is an unsigned long addr that (now) can be either:
> > > 1) an IO token coming from a legacy pci device
> > > 2) a phys address that lives on
rg; John Garry;
> > > will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> > > Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> > > b...@kernel.crashing.org; zourongr...@gmail.com;
> liviu.du...@arm.com;
> > > kant...@163.com
> > > Subject: Re
rg; John Garry;
> > > will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> > > Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> > > b...@kernel.crashing.org; zourongr...@gmail.com;
> liviu.du...@arm.com;
> > > kant...@163.com
> > > Subject: Re
r...@vger.kernel.org;
> > b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> > kant...@163.com
> > Subject: Re: [PATCH V3 2/4] ARM64 LPC: LPC driver implementation on
> > Hip06
> >
> > On Friday, September 23, 2016 12:27:17 AM CEST zhichang
r...@vger.kernel.org;
> > b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> > kant...@163.com
> > Subject: Re: [PATCH V3 2/4] ARM64 LPC: LPC driver implementation on
> > Hip06
> >
> > On Friday, September 23, 2016 12:27:17 AM CEST zhichang
x-...@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subjec
x-...@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subjec
On Friday, September 23, 2016 12:27:17 AM CEST zhichang.yuan wrote:
> For this patch sketch, I have a question.
> Do we call pci_address_to_pio in arch_of_address_to_pio to get the
> corresponding logical IO port
> for LPC??
No, of course not, that would be silly:
The argument to
On Friday, September 23, 2016 12:27:17 AM CEST zhichang.yuan wrote:
> For this patch sketch, I have a question.
> Do we call pci_address_to_pio in arch_of_address_to_pio to get the
> corresponding logical IO port
> for LPC??
No, of course not, that would be silly:
The argument to
On 09/22/2016 08:14 PM, Arnd Bergmann wrote:
On Thursday, September 22, 2016 11:55:45 AM CEST Gabriele Paoloni wrote:
I think extending of_empty_ranges_quirk() may be a reasonable
solution.
What do you think Arnd?
I don't really like that idea, that quirk is meant to work around
broken DTs,
On 09/22/2016 08:14 PM, Arnd Bergmann wrote:
On Thursday, September 22, 2016 11:55:45 AM CEST Gabriele Paoloni wrote:
I think extending of_empty_ranges_quirk() may be a reasonable
solution.
What do you think Arnd?
I don't really like that idea, that quirk is meant to work around
broken DTs,
;
linux-...@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
kant...@163.com
Subject: Re: [PATCH V3 2/4
;
linux-...@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
kant...@163.com
Subject: Re: [PATCH V3 2/4
@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subject: Re:
@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subject: Re:
On Thursday, September 22, 2016 2:47:14 PM CEST Gabriele Paoloni wrote:
> > > static int of_empty_ranges_quirk(struct device_node *np)
> > > {
> > > if (IS_ENABLED(CONFIG_PPC)) {
> > > @@ -503,7 +512,7 @@ static int of_translate_one(struct device_node
> > *parent, struct of_bus *bus,
> >
On Thursday, September 22, 2016 2:47:14 PM CEST Gabriele Paoloni wrote:
> > > static int of_empty_ranges_quirk(struct device_node *np)
> > > {
> > > if (IS_ENABLED(CONFIG_PPC)) {
> > > @@ -503,7 +512,7 @@ static int of_translate_one(struct device_node
> > *parent, struct of_bus *bus,
> >
@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subject: Re:
@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subject: Re:
On Thursday, September 22, 2016 11:55:45 AM CEST Gabriele Paoloni wrote:
> > > I think extending of_empty_ranges_quirk() may be a reasonable
> > solution.
> > > What do you think Arnd?
> >
> > I don't really like that idea, that quirk is meant to work around
> > broken DTs, but we can just make
On Thursday, September 22, 2016 11:55:45 AM CEST Gabriele Paoloni wrote:
> > > I think extending of_empty_ranges_quirk() may be a reasonable
> > solution.
> > > What do you think Arnd?
> >
> > I don't really like that idea, that quirk is meant to work around
> > broken DTs, but we can just make
@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subject: Re:
@vger.kernel.org; gre...@linuxfoundation.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; Yuanzhichang;
> Linuxarm; xuwei (O); linux-ser...@vger.kernel.org;
> b...@kernel.crashing.org; zourongr...@gmail.com; liviu.du...@arm.com;
> kant...@163.com
> Subject: Re:
On Wednesday, September 21, 2016 4:20:55 PM CEST Gabriele Paoloni wrote:
> > -Original Message-
> > From: zhichang [mailto:zhichang.yua...@gmail.com]
> > On 2016年09月15日 20:24, Arnd Bergmann wrote:
> > > On Thursday, September 15, 2016 12:05:51 PM CEST Gabriele Paoloni
> > wrote:
> > >>>
On Wednesday, September 21, 2016 4:20:55 PM CEST Gabriele Paoloni wrote:
> > -Original Message-
> > From: zhichang [mailto:zhichang.yua...@gmail.com]
> > On 2016年09月15日 20:24, Arnd Bergmann wrote:
> > > On Thursday, September 15, 2016 12:05:51 PM CEST Gabriele Paoloni
> > wrote:
> > >>>
...@acm.org; linux-...@vger.kernel.org;
> gre...@linuxfoundation.org; John Garry; will.dea...@arm.com; linux-
> ker...@vger.kernel.org; Yuanzhichang; Linuxarm; xuwei (O); linux-
> ser...@vger.kernel.org; b...@kernel.crashing.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com
>
...@acm.org; linux-...@vger.kernel.org;
> gre...@linuxfoundation.org; John Garry; will.dea...@arm.com; linux-
> ker...@vger.kernel.org; Yuanzhichang; Linuxarm; xuwei (O); linux-
> ser...@vger.kernel.org; b...@kernel.crashing.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com
>
Hi, Arnd,
On 2016年09月15日 20:24, Arnd Bergmann wrote:
> On Thursday, September 15, 2016 12:05:51 PM CEST Gabriele Paoloni wrote:
>>> -Original Message-
>>> On Thursday, September 15, 2016 8:02:27 AM CEST Gabriele Paoloni wrote:
From <<3.1.1. Open Firmware Properties for Bus
Hi, Arnd,
On 2016年09月15日 20:24, Arnd Bergmann wrote:
> On Thursday, September 15, 2016 12:05:51 PM CEST Gabriele Paoloni wrote:
>>> -Original Message-
>>> On Thursday, September 15, 2016 8:02:27 AM CEST Gabriele Paoloni wrote:
From <<3.1.1. Open Firmware Properties for Bus
.kernel.org;
> gre...@linuxfoundation.org; John Garry; will.dea...@arm.com; linux-
> ker...@vger.kernel.org; Yuanzhichang; Linuxarm; xuwei (O); linux-
> ser...@vger.kernel.org; b...@kernel.crashing.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com;
> zhichang.yua...@gmail.com
> S
.kernel.org;
> gre...@linuxfoundation.org; John Garry; will.dea...@arm.com; linux-
> ker...@vger.kernel.org; Yuanzhichang; Linuxarm; xuwei (O); linux-
> ser...@vger.kernel.org; b...@kernel.crashing.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com;
> zhichang.yua...@gmail.com
> S
On Thursday, September 15, 2016 12:05:51 PM CEST Gabriele Paoloni wrote:
> > -Original Message-
> > On Thursday, September 15, 2016 8:02:27 AM CEST Gabriele Paoloni wrote:
> > >
> > > From <<3.1.1. Open Firmware Properties for Bus Nodes>> in
> > >
On Thursday, September 15, 2016 12:05:51 PM CEST Gabriele Paoloni wrote:
> > -Original Message-
> > On Thursday, September 15, 2016 8:02:27 AM CEST Gabriele Paoloni wrote:
> > >
> > > From <<3.1.1. Open Firmware Properties for Bus Nodes>> in
> > >
.@linuxfoundation.org; b...@kernel.crashing.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; xuwei (O); Linuxarm;
> linux-ser...@vger.kernel.org; linux-...@vger.kernel.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com;
> zhichang.yua...@gmail.com
&g
.@linuxfoundation.org; b...@kernel.crashing.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; xuwei (O); Linuxarm;
> linux-ser...@vger.kernel.org; linux-...@vger.kernel.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com;
> zhichang.yua...@gmail.com
&g
On Thursday, September 15, 2016 8:02:27 AM CEST Gabriele Paoloni wrote:
>
> From <<3.1.1. Open Firmware Properties for Bus Nodes>> in
> http://www.firmware.org/1275/bindings/isa/isa0_4d.ps
>
> I quote:
> "There shall be an entry in the "ranges" property for each
> of the Memory and/or I/O
On Thursday, September 15, 2016 8:02:27 AM CEST Gabriele Paoloni wrote:
>
> From <<3.1.1. Open Firmware Properties for Bus Nodes>> in
> http://www.firmware.org/1275/bindings/isa/isa0_4d.ps
>
> I quote:
> "There shall be an entry in the "ranges" property for each
> of the Memory and/or I/O
.@linuxfoundation.org; b...@kernel.crashing.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; xuwei (O); Linuxarm;
> linux-ser...@vger.kernel.org; linux-...@vger.kernel.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com;
> zhichang.yua...@gmail.com
&g
.@linuxfoundation.org; b...@kernel.crashing.org; John Garry;
> will.dea...@arm.com; linux-kernel@vger.kernel.org; xuwei (O); Linuxarm;
> linux-ser...@vger.kernel.org; linux-...@vger.kernel.org;
> zourongr...@gmail.com; liviu.du...@arm.com; kant...@163.com;
> zhichang.yua...@gmail.com
&g
On Wednesday, September 14, 2016 10:50:44 PM CEST zhichang.yuan wrote:
>
> On 2016/9/14 20:33, Arnd Bergmann wrote:
> > On Wednesday, September 14, 2016 8:15:52 PM CEST Zhichang Yuan wrote:
> >
> >> +Required properties:
> >> +- compatible: should be "hisilicon,low-pin-count"
> >> +-
On Wednesday, September 14, 2016 10:50:44 PM CEST zhichang.yuan wrote:
>
> On 2016/9/14 20:33, Arnd Bergmann wrote:
> > On Wednesday, September 14, 2016 8:15:52 PM CEST Zhichang Yuan wrote:
> >
> >> +Required properties:
> >> +- compatible: should be "hisilicon,low-pin-count"
> >> +-
On 2016/9/14 20:33, Arnd Bergmann wrote:
> On Wednesday, September 14, 2016 8:15:52 PM CEST Zhichang Yuan wrote:
>
>> +Required properties:
>> +- compatible: should be "hisilicon,low-pin-count"
>> +- #address-cells: must be 2 which stick to the ISA/EISA binding doc.
>> +- #size-cells: must be 1
On 2016/9/14 20:33, Arnd Bergmann wrote:
> On Wednesday, September 14, 2016 8:15:52 PM CEST Zhichang Yuan wrote:
>
>> +Required properties:
>> +- compatible: should be "hisilicon,low-pin-count"
>> +- #address-cells: must be 2 which stick to the ISA/EISA binding doc.
>> +- #size-cells: must be 1
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc6 next-20160914]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc6 next-20160914]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to
On Wednesday, September 14, 2016 8:15:52 PM CEST Zhichang Yuan wrote:
> +Required properties:
> +- compatible: should be "hisilicon,low-pin-count"
> +- #address-cells: must be 2 which stick to the ISA/EISA binding doc.
> +- #size-cells: must be 1 which stick to the ISA/EISA binding doc.
> +- reg:
On Wednesday, September 14, 2016 8:15:52 PM CEST Zhichang Yuan wrote:
> +Required properties:
> +- compatible: should be "hisilicon,low-pin-count"
> +- #address-cells: must be 2 which stick to the ISA/EISA binding doc.
> +- #size-cells: must be 1 which stick to the ISA/EISA binding doc.
> +- reg:
64 matches
Mail list logo
