This patch renames to avoid camelcase, changes follow are:
- pu8Buffer to buffer
- u32BufferLen to buffer_len
- ppstrConnectRespInfo to ret_connect_resp_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 16
drivers/staging/wilc1000/coreconfigurator
This patch renames to avoid camelcase, changes follow are:
- pstrConnectRespInfo to connect_resp_info
- u16AssocRespLen to assoc_resp_len
- pu8IEs to ies
- u16IEsLen to ies_len
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 34 ++---
1 file c
This patch renames to avoid camelcase, changes follow are:
- pstrConnectRespInfo to connect_resp_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 14 +++---
drivers/staging/wilc1000/coreconfigurator.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
This patch renames to avoid camelcase, changes follow are:
- pstrNetworkInfo to network_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 14 +++---
drivers/staging/wilc1000/coreconfigurator.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --
This patch renames to avoid camelcase, changes follow are:
- pu8TimElm to tim_elm
- pu8IEs to ies
- u16IEsLen to ies_len
- u32Tsf_Lo to tsf_lo
- u32Tsf_Hi to tsf_hi
And, remove the prefix variable defined name, below are:
- u8index to index
- pu8msa to msa
Signed-off-by: Leo Kim
---
driv
There are over-commenting in the coreconfigurator.c file and most of them
are not helpful to explain what the code does and generate 80 ending
line over warnings. So, all of comments are removed in this patch and the
comments will later be added if necessary with the preferred Linux style.
Signed-
This patch renames u16RxLen variable to rx_len to avoid camelcase.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/wilc1000
This patch renames to avoid camelcase, changes follow are:
- pu8MsgBuffer to msg_buffer
- ppstrNetworkInfo to ret_network_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 16
drivers/staging/wilc1000/coreconfigurator.h | 2 +-
2 files changed, 9 i
This patch renames variable s32Error to result
to avoid CamelCase naming convention.
Also, remove the unused variable s32Error and replace with direct return.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 19 +--
1 file changed, 9 insertions(+), 10 dele
This patch renames to avoid camelcase, changes follow are:
- pstrNetworkInfo to network_info
- u8MsgType to msg_type
- u8MsgID to msg_id
- u16MsgLen to msg_len
- u16WidID to wid_id
- u16WidLen to wid_len
- pu8WidVal to wid_val
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfig
This patch renames u16index variable to index
to remove the prefix variable defined name.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers
This patch renames u16TagParamOffset variable to tag_param_offset
to avoid camelcase.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/wilc
Hi,
On 2016/1/20 6:40, David Rientjes wrote:
> On Tue, 19 Jan 2016, Chen Feng wrote:
>
>> When a process fork a child process, we should not allow the
>> child process use the binder which opened by parent process.
>>
>> But if the binder-object creater is a thread of one process who exit,
>> the
On Wed, 2016-01-27 at 23:29 -0800, K. Y. Srinivasan wrote:
> tree: https://na01.safelinks.protection.outlook.com/?url=https%3a%2
> f%2fgit.kernel.org%2fpub%2fscm%2flinux%2fkernel%2fgit%2ftorvalds%2fli
> nux.git&data=01%7c01%7ckys%40microsoft.com%7ce2e0622715844b79ad7108d3
> 2796ec3c%7c72f988bf86f
tree:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit.kernel.org%2fpub%2fscm%2flinux%2fkernel%2fgit%2ftorvalds%2flinux.git&data=01%7c01%7ckys%40microsoft.com%7ce2e0622715844b79ad7108d32796ec3c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ubr4GbBaNS%2ftOz%2buJBk0CL9N0UNG9x2Ti
From: Kamal Mostafa
Use the local uapi headers to keep in sync with "recently" added #define's
(e.g. VSS_OP_REGISTER1).
Fixes: 3eb2094c59e8 ("Adding makefile for tools/hv")
Cc:
Signed-off-by: Kamal Mostafa
Signed-off-by: K. Y. Srinivasan
---
tools/hv/Makefile |2 ++
1 files changed, 2 in
From: Dexuan Cui
The hvsock driver needs this API to release all the resources related
to the channel.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c | 33 -
drivers/hv/connection.c |4 ++--
include/linux/hyperv.
From: Dexuan Cui
This will be used by the coming net/hvsock driver.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
include/linux/hyperv.h |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index 3172521.
The function hv_ringbuffer_read() is called always on a pre-assigned
CPU. Each chnnel is bound to a specific CPU and this function is
always called on the CPU the channel is bound. There is no need to
acquire the spin lock; get rid of this overhead.
Signed-off-by: K. Y. Srinivasan
---
drivers/hv
From: Vitaly Kuznetsov
When we pick a CPU to use for a new subchannel we try find a non-used one
on the appropriate NUMA node, we keep track of them with the
primary->alloced_cpus_in_node mask. Under normal circumstances we don't run
out of available CPUs but it is possible when we we don't initi
From: Dexuan Cui
A function to send the type of message is also added.
The coming net/hvsock driver will use this function to proactively request
the host to offer a VMBus channel for a new hvsock connection.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c
On the channel send side, many of the VMBUS
device drivers explicity serialize access to the
outgoing ring buffer. Give more control to the
VMBUS device drivers in terms how to serialize
accesss to the outgoing ring buffer.
The default behavior will be to aquire the
ring lock to preserve the curren
From: Dexuan Cui
Only the coming hv_sock driver has a "true" value for this flag.
We treat the hvsock offers/channels as special VMBus devices.
Since the hv_sock driver handles all the hvsock offers/channels, we need to
tweak vmbus_match() for hv_sock driver, so we introduce this flag.
Signed-o
From: Vitaly Kuznetsov
We have to call vmbus_initiate_unload() on crash to make kdump work but
the crash can also be happening in interrupt (e.g. Sysrq + c results in
such) where we can't schedule or the following will happen:
[ 314.905786] bad: scheduling from the idle thread!
Just skipping t
From: Dexuan Cui
When the hvsock channel's outbound ringbuffer is full (i.e.,
hv_ringbuffer_write() returns -EAGAIN), we should avoid the unnecessary
signaling the host.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c |6 +-
1 files changed, 5 insert
From: Dexuan Cui
A helper function is also added.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
include/linux/hyperv.h |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index 4af51a3..79c4aa7 100644
-
From: Vitaly Kuznetsov
clocksource_change_rating() involves mutex usage and can't be called
in interrupt context. It also makes sense to avoid doing redundant work
on crash.
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/hv.c | 10 --
1 files changed,
From: Dexuan Cui
This will be used by the coming hv_sock driver.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c | 11 +++
include/linux/hyperv.h|9 +
2 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/c
Miscellaneous fixes and enhancements.
V2: Fixed a merge error in Drivers: hv: vmbus: add an API
vmbus_hvsock_device_unregister()
Dexuan Cui (7):
Drivers: hv: vmbus: add a helper function to set a channel's pending
send size
Drivers: hv: vmbus: define the new offer type for Hyper-V socket
> -Original Message-
> From: K. Y. Srinivasan [mailto:k...@microsoft.com]
> Sent: Wednesday, January 27, 2016 4:27 PM
> To: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> vkuzn...@redhat.com; jasow...@redhat.
The default timeout routine used for FC transport is not
suitable for FC devices managed by storvsc since FC devices
managed by storvsc driver do not have an rport associated
with them. Use the time out handler used for SCSI devices
for FC devices as well.
Signed-off-by: K. Y. Srinivasan
Reviewed
The current code assumes that there is only one target in device lookup.
Fix this bug. This will alow us to correctly handle hot reomoval of LUNs.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Alex Ng
Tested-by: Vivek Yadav
---
V2: Made lun and target_id unsigned 8 bit entities - Hannes
Some miscellaneous fixes.
V2: addressed comments from Hannes Reinecke
K. Y. Srinivasan (2):
scsi: storvsc: Install the storvsc specific timeout handler for FC
devices
scsi: storvsc: Use the specified target ID in device lookup
drivers/scsi/storvsc_drv.c | 16 +++-
1 files
On Thu, Jan 28, 2016 at 10:28:38AM +1100, Julian Calaby wrote:
> Hi Greg,
>
> On Thu, Jan 28, 2016 at 10:07 AM, Greg KH wrote:
> > On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
> >> Hi Glen,
> >>
> >> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
> >> > Dan Carpenter write
Hi Greg,
On Thu, Jan 28, 2016 at 10:07 AM, Greg KH wrote:
> On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
>> Hi Glen,
>>
>> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
>> > Dan Carpenter writes:
>> >
>> >> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrot
On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
> Hi Glen,
>
> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
> > Dan Carpenter writes:
> >
> >> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
> >>> Hi All,
> >>>
> >>> I'm helping Greg do a bit of cleanup i
From: Dexuan Cui
A function to send the type of message is also added.
The coming net/hvsock driver will use this function to proactively request
the host to offer a VMBus channel for a new hvsock connection.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c
From: Vitaly Kuznetsov
We have to call vmbus_initiate_unload() on crash to make kdump work but
the crash can also be happening in interrupt (e.g. Sysrq + c results in
such) where we can't schedule or the following will happen:
[ 314.905786] bad: scheduling from the idle thread!
Just skipping t
From: Dexuan Cui
This will be used by the coming net/hvsock driver.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
include/linux/hyperv.h |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index 3172521.
On the channel send side, many of the VMBUS
device drivers explicity serialize access to the
outgoing ring buffer. Give more control to the
VMBUS device drivers in terms how to serialize
accesss to the outgoing ring buffer.
The default behavior will be to aquire the
ring lock to preserve the curren
From: Kamal Mostafa
Use the local uapi headers to keep in sync with "recently" added #define's
(e.g. VSS_OP_REGISTER1).
Fixes: 3eb2094c59e8 ("Adding makefile for tools/hv")
Cc:
Signed-off-by: Kamal Mostafa
Signed-off-by: K. Y. Srinivasan
---
tools/hv/Makefile |2 ++
1 files changed, 2 in
From: Dexuan Cui
Only the coming hv_sock driver has a "true" value for this flag.
We treat the hvsock offers/channels as special VMBus devices.
Since the hv_sock driver handles all the hvsock offers/channels, we need to
tweak vmbus_match() for hv_sock driver, so we introduce this flag.
Signed-o
From: Vitaly Kuznetsov
When we pick a CPU to use for a new subchannel we try find a non-used one
on the appropriate NUMA node, we keep track of them with the
primary->alloced_cpus_in_node mask. Under normal circumstances we don't run
out of available CPUs but it is possible when we we don't initi
From: Dexuan Cui
The hvsock driver needs this API to release all the resources related
to the channel.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c | 36 +++-
drivers/hv/connection.c |4 ++--
include/linux/hype
From: Dexuan Cui
When the hvsock channel's outbound ringbuffer is full (i.e.,
hv_ringbuffer_write() returns -EAGAIN), we should avoid the unnecessary
signaling the host.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c |6 +-
1 files changed, 5 insert
From: Vitaly Kuznetsov
clocksource_change_rating() involves mutex usage and can't be called
in interrupt context. It also makes sense to avoid doing redundant work
on crash.
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/hv.c | 10 --
1 files changed,
The function hv_ringbuffer_read() is called always on a pre-assigned
CPU. Each chnnel is bound to a specific CPU and this function is
always called on the CPU the channel is bound. There is no need to
acquire the spin lock; get rid of this overhead.
Signed-off-by: K. Y. Srinivasan
---
drivers/hv
From: Dexuan Cui
A helper function is also added.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
include/linux/hyperv.h |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index 4af51a3..79c4aa7 100644
-
From: Dexuan Cui
This will be used by the coming hv_sock driver.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c | 11 +++
include/linux/hyperv.h|9 +
2 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/c
Miscellaneous fixes and enhancements.
Dexuan Cui (7):
Drivers: hv: vmbus: add a helper function to set a channel's pending
send size
Drivers: hv: vmbus: define the new offer type for Hyper-V socket
(hvsock)
Drivers: hv: vmbus: vmbus_sendpacket_ctl: hvsock: avoid unnecessary
signa
Hi Glen,
On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
> Dan Carpenter writes:
>
>> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
>>> Hi All,
>>>
>>> I'm helping Greg do a bit of cleanup in the staging tree, I noticed that
>>> wlan-ng driver is maybe ready to be moved
This patch implements ni_ao_reset much more closely organized like NI MHDDK
examples and DAQ-STC pseudo-code. Adds comments with some more specific
references to the DAQ-STC.
Signed-off-by: Spencer E. Olson
---
drivers/staging/comedi/drivers/ni_mio_common.c | 70 +-
1 fi
These patches implement a proposal to very slightly extend the interpretation of
cmd->stop_arg when cmd->stop_src == TRIG_NONE. Normally, for output subdevices,
when the user specifies cmd->stop_src == TRIG_NONE, the device should
continuously output data that must also be continually fed by the u
This patch implements ni_ao_cmd much more closely organized like NI MHDDK
examples and DAQ-STC pseudo-code. Adds comments with some more specific
references to the DAQ-STC.
For stop_src==TRIG_NONE (continuous output mode of entire buffer), the
count for the UC counter was corrected to represent t
This change enables the mite DMA controller to only transfer the amount of
data needed by a command. By default, the old behavior of transferring the
entire comedi DMA data buffer is still in effect. These changes allow a
command to only transmit a limited portion of that data buffer as needed.
This patch continues the implementation of reinterpreting stop_arg when
stop_src == TRIG_NONE for national instruments cdio output on e/m-series
devices. This is part of a series of patches that allow a user to have a
specific buffer repeated as-is indefinitely. The contents of the DMA
buffer can
This patch implements for analog output the reinterpretation of stop_arg
when stop_src == TRIG_NONE to allow the user to specify the length of the
buffer that should be repeated. The intent is to allow a user to have a
specific buffer repeated as-is indefinitely. The contents of the DMA
buffer ca
Bits NISTC_AO_CMD1_DAC0_UPDATE_MODE and NISTC_AO_CMD1_DAC1_UPDATE_MODE are
now saved in the local copy of the AO_CMD1 register. This is more
appropriate than prior methods of setting these bits specifically _both_
in the ni_ao_cmd configuration function _and_ the ni_ao_inttrig trigger
function. W
Hi Emil,
2016-01-27 Emil Velikov :
> Hi Gustavo,
>
> On 27 January 2016 at 17:03, Gustavo Padovan wrote:
> > Hi Maarten,
> >
> > 2016-01-27 Maarten Lankhorst :
> >
> >> Hey,
> >>
> >> Op 27-01-16 om 14:30 schreef Gustavo Padovan:
> >> > From: Gustavo Padovan
> >> >
> >> > sync_file is useful t
Dan Carpenter writes:
> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
>> Hi All,
>>
>> I'm helping Greg do a bit of cleanup in the staging tree, I noticed that
>> wlan-ng driver is maybe ready to be moved out of staging. Are there
>> any TODO tasks left to do beside checkpa
Hi Gustavo,
On 27 January 2016 at 17:03, Gustavo Padovan wrote:
> Hi Maarten,
>
> 2016-01-27 Maarten Lankhorst :
>
>> Hey,
>>
>> Op 27-01-16 om 14:30 schreef Gustavo Padovan:
>> > From: Gustavo Padovan
>> >
>> > sync_file is useful to connect one or more fences to the file. The file is
>> > used
Hi Maarten,
2016-01-27 Maarten Lankhorst :
> Hey,
>
> Op 27-01-16 om 14:30 schreef Gustavo Padovan:
> > From: Gustavo Padovan
> >
> > sync_file is useful to connect one or more fences to the file. The file is
> > used by userspace to track fences.
> >
> > Signed-off-by: Gustavo Padovan
> >
> I
你的老朋友邀你来Q群:343257759
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Hey,
Op 27-01-16 om 14:30 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> sync_file is useful to connect one or more fences to the file. The file is
> used by userspace to track fences.
>
> Signed-off-by: Gustavo Padovan
>
Is there a value in keeping the abi unchanged?
If not, then Document
From: Gustavo Padovan
We can glue the sw_sync file operations directly on the sync framework
without the need to pass through sw_sync wrappers.
It only builds sw_sync debugfs file support if CONFIG_SW_SYNC is enabled.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Makefile |
From: Gustavo Padovan
As we moved value storage to sync_timeline and fence those two structs
became useless and can be removed now.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 24 +++-
drivers/staging/android/sw_sync.h| 24 ++---
From: Gustavo Padovan
De-stage the remaining bit of sync framework: sync_timeline and sw_sync
plus some debugging routines.
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/Kconfig| 10 +++
drivers/dma-buf/Makefile | 3 +-
.../{stagi
From: Gustavo Padovan
Enable reports of sync_files through /sync/info
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/sync_file.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/dma-buf/sync_file.c b/drivers/dma-buf/sync_file.c
index 92474dd..aa1215d 100644
--- a/drivers/
From: Gustavo Padovan
The .fill_driver_data() ops was just a useless abstraction for
fence_ops op of the same name.
Now that we use fence->seqno to store the value it is cleaner to
remove the abstraction and fill the data directly.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw
From: Gustavo Padovan
Move drv_name, the last field of sync_timeline_ops, to sync_timeline
and remove sync_timeline_ops.
struct sync_timeline_ops was just an extra abstraction on top of
fence_ops, and in the last few commits we removed all it ops in favor
of cleaner fence_ops.
Signed-off-by: Gu
From: Gustavo Padovan
We are moving out of staging/adroid so rename it to a name that is not
related to android anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --gi
From: Gustavo Padovan
During the de-stage of sync framework it was easy to keep sync_dump() out
to avoid an early de-stage of all debug code, but now that sync_debug.c
was de-staged bring sync_dump() back.
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/sync_file.c | 8 ++--
1 file chan
From: Gustavo Padovan
sync_file is useful to connect one or more fences to the file. The file is
used by userspace to track fences.
Signed-off-by: Gustavo Padovan
---
drivers/Kconfig| 2 +
drivers/dma-buf/Kconfig| 11 +
drivers
From: Gustavo Padovan
Now that the value of fence and the timeline are not stored by sw_sync
anymore we can remove this extra abstraction to retrieve this data.
This patch changes both fence_ops (.fence_value_str and
.timeline_value_str) to return the str directly.
It also clean up struct sync_
From: Gustavo Padovan
Now fence timeline is aware of the last signaled fence, as it
receives the increment to the current value in sync_timeline_signal().
That allow us to remove .has_signaled() from timeline_ops as we can
directly compare using timeline->value and fence->seqno in sync.c
Signed
From: Gustavo Padovan
This patch series de-stage the sync framework and it a follow up on the
clean up series I've sent last week:
http://thread.gmane.org/gmane.comp.video.dri.devel/145509
Now in part 2 we finish the de-stage of the sync framework. It start with the
move of sync_file from stagi
That patch adds support for SSD1305 controller.
That is monochrome OLED display controller present in several
displays eq: Winstar WEX012864
Signed-off-by: Alexey Mednyy
---
drivers/staging/fbtft/Kconfig | 6 ++
drivers/staging/fbtft/Makefile | 1 +
drivers/staging/fbtft/fb_ssd1305.
That patch adds support for SSD1325 controller.
That is 4bpp grayscale OLED display controller present in several
displays eq: Winstar WEX012864
Signed-off-by: Alexey Mednyy
---
drivers/staging/fbtft/Kconfig | 6 ++
drivers/staging/fbtft/Makefile | 1 +
drivers/staging/fbtft/fb_ssd1
On Wed, Jan 27, 2016 at 11:22:38AM +0300, Alexey Mednyy wrote:
> On 01/27/2016 02:36 AM, Greg KH wrote:
> > On Tue, Jan 26, 2016 at 07:31:16PM +0300, Alexey Mednyy wrote:
> >> Signed-off-by: Alexey Mednyy
> > Why?
> Sorry, that was required by some other project I sent patches to.
No, the signed-
On 01/27/2016 02:36 AM, Greg KH wrote:
> On Tue, Jan 26, 2016 at 07:31:16PM +0300, Alexey Mednyy wrote:
>> Signed-off-by: Alexey Mednyy
> Why?
Sorry, that was required by some other project I sent patches to.
>
> I can't take patches without any changelog entries, sorry, we need some
> more inform
That patch adds support for SSD1305 controller.
That is monochrome OLED display controller present in several
displays eq: Winstar WEX012864
---
drivers/staging/fbtft/Kconfig | 6 ++
drivers/staging/fbtft/Makefile | 1 +
drivers/staging/fbtft/fb_ssd1305.c | 216 +++
That patch adds support for SSD1325 controller.
That is 4bpp grayscale OLED display controller present in several
displays eq: Winstar WEX012864
---
drivers/staging/fbtft/Kconfig | 6 ++
drivers/staging/fbtft/Makefile | 1 +
drivers/staging/fbtft/fb_ssd1325.c | 205 +++
82 matches
Mail list logo
