Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1683655
| From | Andy Shevchenko <andy.shevchenko@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. |
| Date | 2017-07-08 23:30 +0200 |
| Message-ID | <u15sB-7kS-5@gated-at.bofh.it> (permalink) |
| References | <u0JBL-1Ss-5@gated-at.bofh.it> <u15sB-7kS-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Jul 9, 2017 at 12:12 AM, Peter Rosin <peda@axentia.se> wrote: > On 2017-07-08 00:03, sathyanarayanan.kuppuswamy@linux.intel.com wrote: >> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com> >> >> Currently this driver only provides a single API, mux_control_get() to >> get mux_control reference based on mux_name, and also this API has tight >> dependency on device tree node. For devices, that does not use device >> tree, it makes it difficult to use this API. This patch adds new >> API to access mux_control reference based on device name, chip index and >> controller index value. > > I assume this is for the Intel USB Multiplexer that you sent a driver for > a month or so ago? If so, you still have not answered these questions: > > Is any other consumer in the charts at all? Can this existing consumer > ever make use of some other mux? If the answer to both those questions > are 'no', then I do not see much point in involving the mux subsystem at > all. The Broxton USB PHY driver could just as well write to the register > all by itself, no? > > that I asked in https://lkml.org/lkml/2017/5/31/58 > > What is the point of that driver? Without Heikki's blessing, NAK for this activity. -- With Best Regards, Andy Shevchenko
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. sathyanarayanan.kuppuswamy@linux.intel.com - 2017-07-08 00:10 +0200
[PATCH] mux: fix err_cast.cocci warnings kbuild test robot <lkp@intel.com> - 2017-07-08 22:00 +0200
Re: [PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. kbuild test robot <lkp@intel.com> - 2017-07-08 22:00 +0200
Re: [PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-08 23:30 +0200
Re: [PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. "Kuppuswamy, Sathyanarayanan" <sathyaosid@gmail.com> - 2017-07-09 01:30 +0200
Re: [PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. "Kuppuswamy, Sathyanarayanan" <sathyaosid@gmail.com> - 2017-07-09 01:30 +0200
Re: [PATCH v1 1/1] mux: Add new API to get mux_control ref by device name. sathyanarayanan kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com> - 2017-07-10 23:40 +0200
csiph-web