All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <8739evebv1.fsf@ti.com>

diff --git a/a/1.txt b/N1/1.txt
index 844d6db..a76bb1d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -9,7 +9,7 @@ Govindraj <govindraj.ti@gmail.com> writes:
 >
 >
 >> 1) Use the a custom activate_func in the omap_device pm_lats struct
->>   to idle the first time.
+>> ? to idle the first time.
 >>
 >
 > same activate func gets called for all uarts, how to determine the
@@ -25,12 +25,12 @@ UART device.  After the first call, you could set the activate_func back
 to the default.
 
 >> 2) Use a bus notifier so the device init can be notified when the
->>   real driver is available.  I think you're probably wanting
->>   the BUS_NOTIFY_BIND_DRIVER event, which would happen right
->>   before probe.  There's also BUS_NOTIFY_BOUND_DRIVER which
->>   happens right after probe.   You might actually want to use
->>   both.  e.g.   console_lock(); omap_hwmod_idle() in BIND
->>   and console_unlock() in 'BOUND'.
+>> ? real driver is available. ?I think you're probably wanting
+>> ? the BUS_NOTIFY_BIND_DRIVER event, which would happen right
+>> ? before probe. ?There's also BUS_NOTIFY_BOUND_DRIVER which
+>> ? happens right after probe. ? You might actually want to use
+>> ? both. ?e.g. ? console_lock(); omap_hwmod_idle() in BIND
+>> ? and console_unlock() in 'BOUND'.
 >
 > bus_register_notifier is for all drivers within the bus,
 > omap-uart is registered as platform bus and there a lot more
@@ -45,7 +45,3 @@ The notifier callback passes the device pointer.  You just have to take
 action for the devices you care about, and return for the others.
 
 Kevin
---
-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
diff --git a/a/content_digest b/N1/content_digest
index 048e64d..ce51714 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -6,19 +6,10 @@
  "ref\0CAAL8m4wzT-ecmVeU--EQGF1PxuZuB6WZj54MmVAk-kCtFUcUSg@mail.gmail.com\0"
  "ref\08739ewk3m0.fsf@ti.com\0"
  "ref\0CAAL8m4wgLbmm-3eqku1+0oa77_fxVoFzR1ujF9nwAQRavfqLfg@mail.gmail.com\0"
- "From\0Kevin Hilman <khilman@ti.com>\0"
- "Subject\0Re: [PATCH v6 15/16] OMAP2+: UART: Enable back uart clocks with runtime API for early console\0"
+ "From\0khilman@ti.com (Kevin Hilman)\0"
+ "Subject\0[PATCH v6 15/16] OMAP2+: UART: Enable back uart clocks with runtime API for early console\0"
  "Date\0Fri, 14 Oct 2011 10:12:18 -0700\0"
- "To\0Govindraj <govindraj.ti@gmail.com>\0"
- "Cc\0Govindraj.R <govindraj.raja@ti.com>"
-  linux-omap@vger.kernel.org
-  linux-serial@vger.kernel.org
-  linux-arm-kernel@lists.infradead.org
-  Tony Lindgren <tony@atomide.com>
-  Partha Basak <p-basak2@ti.com>
-  Vishwanath Sripathy <vishwanath.bs@ti.com>
-  Rajendra Nayak <rnayak@ti.com>
- " Santosh Shilimkar <santosh.shilimkar@ti.com>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Govindraj <govindraj.ti@gmail.com> writes:\n"
@@ -32,7 +23,7 @@
  ">\n"
  ">\n"
  ">> 1) Use the a custom activate_func in the omap_device pm_lats struct\n"
- ">> \302\240 to idle the first time.\n"
+ ">> ? to idle the first time.\n"
  ">>\n"
  ">\n"
  "> same activate func gets called for all uarts, how to determine the\n"
@@ -48,12 +39,12 @@
  "to the default.\n"
  "\n"
  ">> 2) Use a bus notifier so the device init can be notified when the\n"
- ">> \302\240 real driver is available. \302\240I think you're probably wanting\n"
- ">> \302\240 the BUS_NOTIFY_BIND_DRIVER event, which would happen right\n"
- ">> \302\240 before probe. \302\240There's also BUS_NOTIFY_BOUND_DRIVER which\n"
- ">> \302\240 happens right after probe. \302\240 You might actually want to use\n"
- ">> \302\240 both. \302\240e.g. \302\240 console_lock(); omap_hwmod_idle() in BIND\n"
- ">> \302\240 and console_unlock() in 'BOUND'.\n"
+ ">> ? real driver is available. ?I think you're probably wanting\n"
+ ">> ? the BUS_NOTIFY_BIND_DRIVER event, which would happen right\n"
+ ">> ? before probe. ?There's also BUS_NOTIFY_BOUND_DRIVER which\n"
+ ">> ? happens right after probe. ? You might actually want to use\n"
+ ">> ? both. ?e.g. ? console_lock(); omap_hwmod_idle() in BIND\n"
+ ">> ? and console_unlock() in 'BOUND'.\n"
  ">\n"
  "> bus_register_notifier is for all drivers within the bus,\n"
  "> omap-uart is registered as platform bus and there a lot more\n"
@@ -67,10 +58,6 @@
  "The notifier callback passes the device pointer.  You just have to take\n"
  "action for the devices you care about, and return for the others.\n"
  "\n"
- "Kevin\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-serial\" in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ Kevin
 
-8e89279455daaa23efb5ec3aed5984edb45cc391897a59c5972351c3e300100b
+512df755140d9fd72a153e99144e203fd8a03c70af38c7c286c0cfb62d4f534b

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.