From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [RFC PATCH v3 1/4] UART: Add UART subsystem as a bus. Date: Thu, 6 Dec 2012 13:40:20 +0000 Message-ID: <20121206134020.0747af0f@bob.linux.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com ([134.134.136.24]:20550 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755022Ab2LFNh4 (ORCPT ); Thu, 6 Dec 2012 08:37:56 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Lv Zheng Cc: Len Brown , Rafael J Wysocki , Greg Kroah-Hartman , Mika Westerberg , linux-acpi@vger.kernel.org, linux-serial@vger.kernel.org > enumerated and userspace can obtain the hotplug event of the UART > target devices. Linux kernel is lack of an overall enumeration > mechanism for UART target devices. ls /sys/class/tty/ > In order to send uevent, a device need to be a class device or a bus > device. This patch introduces a bus_type subsystem to manage the new I still don't see why the existing tty class interfaces cannot be used, the hints from ACPI (or anywhere else) cannot be attached as properties to the tty driver and device sysfs Alan