From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: vcgandhi1@aol.com
Cc: linux-serial@vger.kernel.org
Subject: Re: Change to serial_core.c .... causing my serial driver problem Help Request
Date: Thu, 17 Apr 2008 16:55:23 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804171652010.6716@axis700.grange> (raw)
In-Reply-To: <8CA6E482AE34A65-15A8-47A5@webmail-nb06.sysops.aol.com>
On Wed, 16 Apr 2008, vcgandhi1@aol.com wrote:
> I do the same
>
> port->dev = &dev->dev;
>
> But I am not sure &dev->dev points to the parent. I think it points to the
> device it's self, but I may be wrong. I have tried port->dev = &dev->dev as
> well as port->dev = dev->dev.parent.
It depends on what your "dev" is, and this is driver-specific. So,
unfortunately, I don't think I'll be able to help you any further without
seeing the sources.
> One of these found something when the
> port was TTYS0 but did not work when the port was TTYS2.
>
> Did you test with a non zero port->line. I working on ttyS2.
Yes, I tested it with ttyS0 and ttyS1.
> Just trying to narrow down what could be wrong. It just that
> tty_dev = device_find_child(port->dev, &match, serial_match_port);
>
> is returning NULL for me.
>
> Thank You for your help.
> Vipul
>
> PS. One quick suggestion you may want to check the return value and verify it
> is non-NULL before using it. Makes it easier to debug the code. ...
Feel free to submit a patch.
Thanks
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2008-04-17 14:55 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
2008-04-16 23:11 ` Guennadi Liakhovetski
2008-04-17 2:16 ` vcgandhi1
2008-04-17 14:55 ` Guennadi Liakhovetski [this message]
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=Pine.LNX.4.64.0804171652010.6716@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-serial@vger.kernel.org \
--cc=vcgandhi1@aol.com \
/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