On 26/02/2018 15:07, John Garry wrote:
On 26/02/2018 15:02, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 13:15 +, John Garry wrote:
On 26/02/2018 12:27, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 14:21 +0200, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
On 26/02/2018 15:02, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 13:15 +, John Garry wrote:
On 26/02/2018 12:27, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 14:21 +0200, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
Device (LPC0.CON0) {
Name (_HI
On Mon, 2018-02-26 at 13:15 +, John Garry wrote:
> On 26/02/2018 12:27, Andy Shevchenko wrote:
> > On Mon, 2018-02-26 at 14:21 +0200, Andy Shevchenko wrote:
> > > On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
> >
> >
> > > >Device (LPC0.CON0) {
> > > > Name (_HID, "HISI1031")
On 26/02/2018 12:27, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 14:21 +0200, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
Device (LPC0.CON0) {
Name (_HID, "HISI1031")
// Name (_CID, "PNP0501") // cannot support PNP
One more question. What i
On 26/02/2018 12:21, Andy Shevchenko wrote:
On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
Why you can't do properly in ACPI?
No answer here either.
Sorry, but with this level of communication it's no go for the
series.
Sorry if my answers did not tell you want you want to know.
My
On Mon, 2018-02-26 at 14:21 +0200, Andy Shevchenko wrote:
> On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
> >Device (LPC0.CON0) {
> > Name (_HID, "HISI1031")
> > // Name (_CID, "PNP0501") // cannot support PNP
One more question. What is the problem with this CID? Do you ha
On Mon, 2018-02-26 at 11:56 +, John Garry wrote:
> > > > > > Why you can't do properly in ACPI?
> > > >
> > > > No answer here either.
> > > >
> > > > Sorry, but with this level of communication it's no go for the
> > > > series.
> > > >
> > >
> > > Sorry if my answers did not tell you want
Why you can't do properly in ACPI?
No answer here either.
Sorry, but with this level of communication it's no go for the
series.
Sorry if my answers did not tell you want you want to know.
My point was that the 8250_pnp driver would be used for a pnp_device,
but we are creating a platform d
On Mon, 2018-02-26 at 10:45 +, John Garry wrote:
> > > > > > > for supporting an 8250-compatible UART with
> > > > > > > the following profile/features:
> > > > > > > - platform device
> > > > > > > - polling mode (i.e. no interrupt support)
> > > > > > > - ACPI FW
> > > > > >
> > > > > > El
Hi Andy,
We require it for a development board for our hip06 platform.
Okay, and this particular platform uses Synopsys IP?
As I see this uart is really a virtual 8250, so HW details like apb
clocks and the like are hidden, so may not be relevant.
Good to know.
However I will check with
On Mon, 2018-02-26 at 09:33 +, John Garry wrote:
> On 23/02/2018 17:31, Andy Shevchenko wrote:
> > On Fri, 2018-02-23 at 11:02 +, John Garry wrote:
> > > On 23/02/2018 10:30, Andy Shevchenko wrote:
> > > > On Fri, 2018-02-23 at 02:42 +0800, John Garry wrote:
> > > We require it for a devel
On 23/02/2018 17:31, Andy Shevchenko wrote:
On Fri, 2018-02-23 at 11:02 +, John Garry wrote:
On 23/02/2018 10:30, Andy Shevchenko wrote:
On Fri, 2018-02-23 at 02:42 +0800, John Garry wrote:
There is a requirement
Where?
Hi Andy,
We require it for a development board for our hip06
On Fri, 2018-02-23 at 11:02 +, John Garry wrote:
> On 23/02/2018 10:30, Andy Shevchenko wrote:
> > On Fri, 2018-02-23 at 02:42 +0800, John Garry wrote:
> > > There is a requirement
>
> > Where?
>
> We require it for a development board for our hip06 platform.
Okay, and this particular platfo
On 23/02/2018 10:30, Andy Shevchenko wrote:
On Fri, 2018-02-23 at 02:42 +0800, John Garry wrote:
There is a requirement
Hi Andy,
Where?
We require it for a development board for our hip06 platform. FWIW,
here's a link to a board overview (does not mention UART particulars):
http://ope
On Fri, 2018-02-23 at 02:42 +0800, John Garry wrote:
> There is a requirement
Where?
> for supporting an 8250-compatible UART with
> the following profile/features:
> - platform device
> - polling mode (i.e. no interrupt support)
> - ACPI FW
Elaborate this one, please.
> - IO port iotype
> -
15 matches
Mail list logo
