public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: vcgandhi1@aol.com
To: vcgandhi1@aol.com, g.liakhovetski@gmx.de
Cc: linux-serial@vger.kernel.org
Subject: Re: Change to serial_core.c .... causing my serial driver problem Help Request
Date: Tue, 15 Apr 2008 20:08:01 -0400	[thread overview]
Message-ID: <8CA6D6D112DB4D4-1128-38B0@webmail-nb07.sysops.aol.com> (raw)
In-Reply-To: <8CA6D67D9E313CC-1128-35BB@webmail-nb07.sysops.aol.com>



Guennadi,

I think the issue is when the serial port is embedded and not connected 
through the bus. So I am talking about the drivers in the 
kernel/drivers/serial directory. A few of them use suspend and resume 
and I think they may not be compatible with your change. 

Do you know if you anybody tested any serial ports that are located in 
that directory and use  the suspend and resume calls. Ports not 
connected through the pci  bus.

Vipul



-----Original Message-----
From: vcgandhi1@aol.com
To: g.liakhovetski@gmx.de
Cc: linux-serial@vger.kernel.org
Sent: Tue, 15 Apr 2008 4:30 pm
Subject: Re: Change to serial_core.c .... causing my serial driver 
problem Help Request


Guennadi,

I think the issue is when the serial port is embedded and not connected 
through the bus. So I am talking about the drivers in the 
kernel/drivers/serial directory. A few of them use suspend and resume 
and I think they may not be compatible with your change. I not sure who 
signed off on in but I am having problems with the change and would 
like to like to get it resolved.  

Do you know if you anybody tested any serial ports that are located in 
that directory and use  the suspend and resume calls. Ports not 
connected through a bus.

Vipul




-----Original Message-----
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: vcgandhi1@aol.com
Cc: linux-serial@vger.kernel.org
Sent: Tue, 15 Apr 2008 3:49 pm
Subject: RE: Change to serial_core.c .... causing my serial driver 
problem Help Request



On Tue, 15 Apr 2008, vcgandhi1@aol.com wrote:

> Will do,

I added linux-serial to cc.

> But it seems like the code that was check in has issues.

Given the number and names of signed-off's under this patch, it is 
pretty
unlikely.

> If you look in
> the directory no serial driver properly sets port->dev to be pointing 
to
> the parent. It looks like they all point to themselves. Can you tell 
me
> which driver you tested this change on. I can look to see how they 
set
> port->dev.

8250_pci.c, and I do think it sets it properly in 
pciserial_init_ports().

Thanks
Guennadi

> Vipul?
> ?
>
> -----Original Message-----
> From: Guennadi Liakhovetski [mailto:g.liakhovetski@gmx.de]
> Sent: Tuesday, April 15, 2008 2:50 PM
> To: Gandhi, Vipul
> Subject: Re: Change to serial_core.c .... causing my serial driver 
problem
Help Request
>
> ?
>
> On Tue, 15 Apr 2008, Gandhi, Vipul wrote:
>
> ?
>
> > For my driver the following call is returning a NULL .?????????
>
> >
>
> >?
>
> >
>
> > tty_dev = device_find_child(port->dev, &match, serial_match_port);
>
> >
>
> >?
>
> >
>
> > Any idea? why, previously this was not in serial_core.c but was 
recently
>
> > added by you I believe. Any help would be appreciated.
>
> ?
>
> No, not without seeing the source-code of your driver. Also, please,
>
> direct such questions to the linux-serial or linux-kernel mailing 
list,
>
> you may then additionally CC the person, who you think can help you 
best.
>
> ?
>
> Thanks
>
> Guennadi
>
> ---
>
> Guennadi Liakhovetski
>

---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-04-16  0:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8CA6D5E4DEA920C-1128-2973@webmail-nb07.sysops.aol.com>
2008-04-15 22:49 ` Change to serial_core.c .... causing my serial driver problem Help Request Guennadi Liakhovetski
     [not found]   ` <8CA6D67D9E313CC-1128-35BB@webmail-nb07.sysops.aol.com>
2008-04-16  0:08     ` vcgandhi1 [this message]
2008-04-16 23:11       ` Guennadi Liakhovetski
2008-04-17  2:16         ` vcgandhi1
2008-04-17 14:55           ` Guennadi Liakhovetski
2008-04-17 16:06             ` vcgandhi1
2008-04-17  2:20         ` vcgandhi1
2008-04-17 14:58           ` Guennadi Liakhovetski
2008-04-17 16:41             ` vcgandhi1
2008-04-17 17:19               ` Guennadi Liakhovetski
2008-04-17 22:58                 ` vcgandhi1
2008-04-18 15:04                   ` Guennadi Liakhovetski
2008-04-19  5:23                     ` vcgandhi1
2008-04-23  9:09                       ` Guennadi Liakhovetski
2008-04-24  0:21                         ` vcgandhi1
2008-04-24 14:02                           ` Guennadi Liakhovetski
2008-04-30  7:43                             ` vcgandhi1
2008-05-31 15:33                             ` vcgandhi1
2008-06-21 22:45                               ` [PATCH] Fix serial_match_port() for dynamic major tty-device numbers Guennadi Liakhovetski
2008-06-24 22:22                                 ` Andrew Morton
2008-06-24 22:54                                   ` Guennadi Liakhovetski

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=8CA6D6D112DB4D4-1128-38B0@webmail-nb07.sysops.aol.com \
    --to=vcgandhi1@aol.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-serial@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox