From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Shankarmurthy, Akshay" <akshay.s@ti.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>,
"jamie@jamieiles.com" <jamie@jamieiles.com>,
"swarren@nvidia.com" <swarren@nvidia.com>,
"dianders@chromium.org" <dianders@chromium.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250: Add cpufreq support
Date: Wed, 18 Apr 2012 20:47:01 +0100 [thread overview]
Message-ID: <20120418204701.31238fe7@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <6F6B80BD2E18844D97BB4B51FE3705C83E92A183@DBDE01.ent.ti.com>
> As per my understanding, tty count keeps the count of tty_open and tty_release, that is
> how many open and close happened on the tty device file(/dev/ttyS*).
> The requirement here is a tty count check, if it is greater than zero then only it should
> proceed for further execution.
The physical port has a different lifetime to the struct tty_struct
(which may change many times within the lifetime of the port). You can't
simply go from the port to a tty struct and assume this is safe and will
not change.
> Kindly elaborate more on the same if it's not correct.
Look at how tty_port_tty_get is used
next prev parent reply other threads:[~2012-04-18 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 6:03 Shankarmurthy, Akshay
2012-04-03 9:55 ` Alan Cox
2012-04-05 10:40 ` Shankarmurthy, Akshay
2012-04-05 10:53 ` Alan Cox
2012-04-12 5:21 ` Shankarmurthy, Akshay
2012-04-12 9:47 ` Alan Cox
2012-04-17 9:43 ` Shankarmurthy, Akshay
2012-04-18 19:47 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-13 12:35 Chaithrika U S
2010-01-13 13:44 ` Alan Cox
2010-01-18 13:17 ` Chaithrika U S
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=20120418204701.31238fe7@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akshay.s@ti.com \
--cc=alan@linux.intel.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jamie@jamieiles.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®