On Fri, Oct 28, 2016 at 7:59 PM, Matt Ranostay wrote:
> On Fri, Oct 28, 2016 at 2:53 PM, Hans Verkuil wrote:
>> Hi Matt,
>>
>> On 28/10/16 22:14, Matt Ranostay wrote:
>>>
>>> So want to toss a few thoughts on adding support for thermopile
>>> devices (could be used for FLIR Lepton as well) that o
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Thu Nov 3 05:00:14 CET 2016
media-tree git hash:bd676c0c04ec94bd830b9192e2c33f2c4532278d
media_build git
You are a recipient to Mrs Julie Leach Donation of $3 million USD. Contact (
julieleac...@gmail.com) for claims.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-
I have important transaction for you as next of kin to claim US$18.37m Mail me
on my private email: chimwia...@gmail.com
so I can send you more details
Thanks
Mr.Chim Wai Kim
==MOVE TO INBOX===
DISCLAIMER: This email and any
Hi Todor,
On Tuesday 01 Nov 2016 10:24:26 Todor Tomov wrote:
> On 10/26/2016 09:53 PM, Rob Herring wrote:
> > On Wed, Oct 19, 2016 at 4:21 AM, Laurent Pinchart wrote:
> >> On Wednesday 19 Oct 2016 12:14:55 Todor Tomov wrote:
> >>> On 10/19/2016 11:49 AM, Laurent Pinchart wrote:
> On Friday 14
Hi Kieran,
Thank you for the patch.
On Thursday 27 Oct 2016 15:01:24 Kieran Bingham wrote:
> The upcoming writeback feature of the VSP1 WPF, allows the active output
> of the DU to be written back to memory. On Generation 3 hardware, the DU
> is fed by the LIF, which is in turn fed by the WPF.
>
Hi Kieran,
Thank you for the patch.
On Thursday 27 Oct 2016 15:01:23 Kieran Bingham wrote:
> This reverts commit 3299ba5c0b213be5d911752d40251c1abc1004f7.
>
> The DU output mode does not rely on frames being supplied on the WPF as
> its pipeline is supplied from DRM. For the upcoming WPF writeba
Hi Peter,
Thank you for the patch.
On Wednesday 02 Nov 2016 14:39:59 Peter Ujfalusi wrote:
> With the new dma_request_chan() the client driver does not need to look for
> the DMA resource and it does not need to pass filter_fn anymore.
> By switching to the new API the driver can now support defe
On Wed, Nov 02, 2016 at 02:00:16PM -0700, VDR User wrote:
> > serial_ir driver in rc-core
>
> Which kernel did this happen in? I don't see a sign of it in 4.8.5 and
> I want to make sure that homebrew serial devices still work with lirc
> after this. Are you sure the serial_ir driver you refer to
> serial_ir driver in rc-core
Which kernel did this happen in? I don't see a sign of it in 4.8.5 and
I want to make sure that homebrew serial devices still work with lirc
after this. Are you sure the serial_ir driver you refer to isn't about
a usb-based serial ir?
Thanks for clarity.
--
To unsubs
Hi Ramesh,
On Wednesday 02 Nov 2016 09:00:00 Ramesh Shanmugasundaram wrote:
> Hi Laurent,
>
> Any further thoughts on the SDR format please (especially the comment
> below). I would appreciate your feedback.
>
> >> On Wednesday 12 Oct 2016 15:10:29 Ramesh Shanmugasundaram wrote:
> >>> This patch
Am 02.11.2016 um 11:40 schrieb Andi Shyti:
> Hi,
>
> The main goal is to add support in the rc framework for IR
> transmitters, which currently is only supported by lirc but that
> is not the preferred way.
>
> The last patch adds support for an IR transmitter driven by
> the MOSI line of an SPI
Hi Sean,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to
This has been replaced by the serial_ir driver in rc-core.
Signed-off-by: Sean Young
---
drivers/staging/media/lirc/Kconfig | 13 -
drivers/staging/media/lirc/Makefile |1 -
drivers/staging/media/lirc/lirc_serial.c | 1130 --
3 files changed, 1144 del
Tested with a homebrew serial ir.
Signed-off-by: Sean Young
---
MAINTAINERS |6 +
drivers/media/rc/Kconfig | 17 +
drivers/media/rc/Makefile|1 +
drivers/media/rc/serial_ir.c | 1020 ++
4 files changed, 1044 insertions(+)
On Wed, Nov 02, 2016 at 07:40:04PM +0900, Andi Shyti wrote:
> The main goal is to add support in the rc framework for IR
> transmitters, which currently is only supported by lirc but that
> is not the preferred way.
>
> The last patch adds support for an IR transmitter driven by
> the MOSI line of
On 11/02/2016 04:23 PM, Niklas Söderlund wrote:
Refactor the probe code path to look for the digital subdevice, if one
is found use it just like the driver did before (Gen2 mode) but if it's
not found prepare for a Gen3 mode by registering a pad for the media
controller API to use.
Signed-off-b
On Sat, Oct 29, 2016 at 11:04:32PM +0200, Arnd Bergmann wrote:
> On Thursday, October 13, 2016 10:28:44 PM CEST Sean Young wrote:
> > When receiving a nec repeat, ensure the correct scancode is repeated
> > rather than a random value from the stack. This removes the need
> > for the bogus uninitial
Hello.
On 11/02/2016 04:23 PM, Niklas Söderlund wrote:
These two fields where forgotten when refactoring the format reset code
path. If they are not also reset at the same time as width and hight the
format read using G_FMT will not match realty.
Reality?
Signed-off-by: Niklas Söderlund
Hi
"4:x:y" refers to chroma subsampling, details here:
https://en.wikipedia.org/wiki/Chroma_subsampling. With "YUV 4:4:4" each
pixel has 1 Luma information and 1 Chroma information: 1 Y + 1 Cb + 1 Cr
= 24 bits per pixel.
In top of that, each of the three components (Y, Cb, Cr) can be stored
On Wed, 02 Nov 2016, Markus Heiser wrote:
> Am 02.11.2016 um 12:43 schrieb Jani Nikula :
>
>> On Wed, 24 Aug 2016, Markus Heiser wrote:
>>> From: Markus Heiser
>>>
>>> This extends the method to build only sub-folders to the targets
>>> "latexdocs" and "pdfdocs". To do so, a conf.py in the sub-
Am 02.11.2016 um 12:43 schrieb Jani Nikula :
> On Wed, 24 Aug 2016, Markus Heiser wrote:
>> From: Markus Heiser
>>
>> This extends the method to build only sub-folders to the targets
>> "latexdocs" and "pdfdocs". To do so, a conf.py in the sub-folder is
>> required, where the latex_documents o
When Gen3 support is added to the driver more then chip id will be
different for the different Soc. To avoid a lot of if statements in the
code create a struct chip_info to contain this information.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 49
The rcar-vin driver needs to be part of a media controller to support
Gen3. Give each VIN instance a unique name so it can be referenced from
userspace.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -
Add the register needed to work with Gen3 hardware. This patch adds
the logic for how to work with the Gen3 hardware. More work is required
to enable the subdevice structure needed to configure capturing.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-dma.c | 98 +++
The code to lookup which pad is source and sink can be broken out to a
helper function.
A bad check is also dropped in this refactoring. If the subdeivce don't
supply pad information the driver would not be able to use it if the
check is kept.
Signed-off-by: Niklas Söderlund
---
drivers/media/p
On Gen3 the max supported width and height will be different from Gen2.
Move the limits to the struct chip_info to prepare for Gen3 support.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 6 ++
drivers/media/platform/rcar-vin/rcar-v4l2.c | 6 ++
drivers
Update the driver to retrieve the code and mbus_cfg values from a
rvin_graph_entity retrieved from a wrapper function instead of directly
accessing the entity for the digital port. This is done to prepare for
Gen3 support where the subdeivce might change during runtime, so to
directly accesses a sp
If the subdevice supports dv_timings_cap the driver should not fill in
the standard. Also don't use the standard from probe time ask the
subdevice each time, this is done in preparation for Gen3 support where
the source subdevice might change during runtime.
Signed-off-by: Niklas Söderlund
---
d
The rcar-vin driver only uses one pad, pad number 0.
All v4l2 operations which did not check that the requested operation
was for pad 0 have been updated with a check to enforce this.
All v4l2 operations that stored (and later restore) the requested pad
before substituting it for the subdeivc
Now that the pad information is present in struct rvin_graph_entity use
it when verifying the media bus format.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/rcar-vin/rcar-core.c
b/drive
Some of the parser functions previously only used by the digital
subdevice OF/V4L2 async code will be shared with the CSI2 group
notifiers. Clarify which notifier register error message and mark which
functions are generic helpers.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-
Use rvin_reset_format() in rvin_s_dv_timings() instead if just resetting
a few fields. This fixes an issue where the field format was not
properly set after S_DV_TIMINGS.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 8 ++--
1 file changed, 2 insertions(+)
Move the sink and source pad index from struct rvin_dev to struct
rvin_graph_entity. This is done in preparation of Gen3 support where the
active subdeivce can be changed during runtime. And if the subdevice is
changed the pad numbers are different so it's better to read them a
rvin_graph_entity th
Refactor the probe code path to look for the digital subdevice, if one
is found use it just like the driver did before (Gen2 mode) but if it's
not found prepare for a Gen3 mode by registering a pad for the media
controller API to use.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rc
The rvin_v4l2_probe() handler will with Gen3 support need to handle more
then one subdevice. To prepare for this move the digital subdev pad
number discover to the digital specific async notification complete
function.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core
This is done to prepare for Gen3 support where there can be more then
one video pipeline which can terminate in a particular VIN instance.
Each pipeline have its own set of subdevices so to attach to a specific
subdevice at probe time is not possible. The pipelines will be
configured using the medi
Each Gen3 SoC have a limited set of predefined routing possibilities for
which CSI2 device and virtual channel can be routed to which VIN
instance. Prepare to store this information in the struct rvin_info.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-vin.h | 16
On Gen3 all VIN instances which wish to interact with with the shared
CSI2 resource needs to be part of the same media device and share other
information, such as subdevices and be able to call routing operations
on other VIN instances.
This patch adds a group allocator which joins all VIN instanc
Document the Gen3 devicetree bindings. The new bindings are all handled
in the port@1 node, if a endpoint is described as on Gen2 in port@0 the
driver will work in Gen2 mode and this is supported on Gen3. The new
CSI-2 video sources are only supported on Gen3.
Signed-off-by: Niklas Söderlund
---
Add the SoC specific information for Renesas Salvator-X M3 (r8a7796)
board.
Signed-off-by: Niklas Söderlund
---
.../devicetree/bindings/media/rcar_vin.txt | 1 +
drivers/media/platform/rcar-vin/rcar-core.c| 63 ++
2 files changed, 64 insertions(+)
diff --git
Add the ability to process media device link change request. Link
enablement are a bit complicated on Gen3, if it's possible to enable a
link depends on what other links already are enabled. On Gen3 the 8 VIN
are split into two subgroups (VIN0-3 and VIN4-7) and from a routing
perspective these two
On Gen3 the CSI2 bridge stream needs to be start/stop in conjunction
with the video source. Create helpers to deal with both the Gen2 single
subdevice case and the Gen3 CSI2 group case.
In the Gen3 case there might be other simultaneous users of the bridge
and source devices so examine each entity
Attempt to attach to the subdevices pointed out by the routing from the
CSI2 group when the video device is opened. This is the last piece
missing to enable CSI2 groups on Gen3.
If the current CSI2 routing for the group points ta a set of subdevices
which are not present (not all routings are avai
The CSI2 bridge needs to know the video format, propagate it after the
video source have had its say on the format.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/media/platform/rcar-vin
On Gen3 the CSI routing is controlled by the VnCSI_IFMD register. One
feature of this register is that it's only present in the VIN0 and VIN4
instances. The register in VIN0 controls the routing for VIN0-3 and the
register in VIN4 controls routing for VIN4-7.
To be able to control routing from a m
On Gen3 there might be a CSI2 bridge between the video source and the
VIN. Add helpers to check for this and to fetch the bridge subdevice.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 19 +++
drivers/media/platform/rcar-vin/rcar-vin.h | 2 +
Add the SoC specific information for Renesas Salvator-X H3 (r8a7795)
board.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/Kconfig | 2 +-
drivers/media/platform/rcar-vin/rcar-core.c | 71 +
2 files changed, 72 insertions(+), 1 deletion(-)
d
Make the subdevice helpers look not only at the local digital subdevice
but also for the CSI2 group subdevices which can be present on Gen3.
Which CSI2 group subdevices are found depends on the CSI2 subgroup
routing which is stored in the CHSEL register of the subgroup master
(VIN0 for VIN0-3 and
Parse the VIN Gen3 OF graph and register all devices in the CSI2 group
common media device. Once a subdevice is added to the common media
device list as many links as possible are added and if possible enabled.
The links between the video source device and the CSI2 bridge are
enabled as immutable
From: Laurent Pinchart
This is a wrapper around the media entity has_route operation.
Signed-off-by: Laurent Pinchart
Signed-off-by: Michal Simek
Signed-off-by: Niklas Söderlund
---
drivers/media/media-entity.c | 29 +
include/media/media-entity.h | 3 +++
2 file
These two fields where forgotten when refactoring the format reset code
path. If they are not also reset at the same time as width and hight the
format read using G_FMT will not match realty.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 3 +++
1 file changed,
From: Laurent Pinchart
The optional operation can be used by entities to report whether two
pads are internally connected.
Signed-off-by: Laurent Pinchart
Signed-off-by: Michal Simek
Signed-off-by: Niklas Söderlund
---
include/media/media-entity.h | 5 +
1 file changed, 5 insertions(+)
Hi All,
This series enable Gen3 VIN support in rcar-vin driver for Renesas
r8a7795 and r8a7796. It is based on top of v4.9-rc3.
Parts of this series was previously part of an different series from me
which enabled Gen3 support in a different way (using s_input instead of
a media controller) bu
The functionality provided by rvin_s_fmt_vid_cap() will be needed in
other places to add Gen3 support. Split it up in a function which do the
work and one which interface with the v4l2 API.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 12 +---
1 file
A V4L2 driver for Renesas R-Car MIPI CSI-2 interface. The driver
supports the rcar-vin driver on R-Car Gen3 SoCs where a separate driver
is needed to receive CSI-2.
Driver is based on a prototype by Koji Matsuoka in the Renesas BSP.
Signed-off-by: Niklas Söderlund
---
Changes since v2:
- Added
Hi Laurent,
Any further thoughts on the SDR format please (especially the comment below). I
would appreciate your feedback.
> > On Wednesday 12 Oct 2016 15:10:29 Ramesh Shanmugasundaram wrote:
> > > This patch adds documentation for the three new SDR formats
> > >
> > > V4L2_SDR_FMT_SCU16BE
> >
On 10/30/2016 02:53 AM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return error code -ENODEV from the error handling
> case instead of 0, as done elsewhere in this function.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/media/platform/sti/c8sectpfe/c8sectpfe-core.c | 2 ++
> 1 file c
Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Amir A. Khanmammadov
RE
From: Hans Verkuil
The last open issues have been addressed, so it is time to move
this out of staging and into the mainline and to move the public
cec headers to include/uapi/linux.
Signed-off-by: Hans Verkuil
---
Changes since v1:
Fix path to cec.h in Documentation/media/Makefile.
Forgot to
Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Amir A. Khanmammadov
RE
From: Hans Verkuil
The CEC_MSG_INITIATE_ARC message is special since it is the ONLY
CEC message that accepts two possible valid replies:
CEC_MSG_REPORT_ARC_INITIATED and CEC_MSG_REPORT_ARC_TERMINATED.
So if the transmitted message is CEC_MSG_INITIATE_ARC and the remote
side replied with CEC_MSG
From: Hans Verkuil
When the persistent state is restored, the all_device_types field
was never filled in. Fix this.
Signed-off-by: Hans Verkuil
---
drivers/staging/media/pulse8-cec/pulse8-cec.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/staging/media/pulse8-cec/pulse8-
From: Hans Verkuil
As per the CEC specification:
- CEC messages with a too-small payload should be ignored.
- Broadcast messages that are only allowed as directed messages
should be ignored.
- Directed messages that are only allowed as broadcast messages
should be ignored.
Implement this in
From: Hans Verkuil
Update the TODOs explaining why these two drivers remain in
staging. The reason is that these drivers rely on userspace to
set the physical address, but that should come from the HDMI
output driver. This in turn needs the upcoming HDMI notifier
framework.
Signed-off-by: Hans V
From: Hans Verkuil
Now that the CEC framework has been moved out of staging and into the
mainline kernel we can do the same for the pulse8-cec driver.
Signed-off-by: Hans Verkuil
---
drivers/media/usb/Kconfig | 5 +++
drivers/media/usb/Makefile
From: Hans Verkuil
This patch series makes the final changes so that the cec framework
and the pulse8-cec driver can be moved out of staging.
The first patch fixes a pulse8-cec bug, the second removes the
spurious 'row' comments in the cec documentation using Laurent's script
(Thanks Laurent!).
From: Hans Verkuil
This uses Laurent's python script to convert all tables, dropping
the useless 'row' comments.
See commit c2b66cafdf02 ("[media] v4l: doc: Remove row numbers from tables")
for the script that was used.
Signed-off-by: Hans Verkuil
---
.../media/uapi/cec/cec-ioc-adap-g-caps.rs
From: Hans Verkuil
The cec framework and the pulse8-cec driver have been moved out
of staging, so update the MAINTAINERS paths.
Signed-off-by: Hans Verkuil
---
MAINTAINERS | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 93e9f42..51
From: Hans Verkuil
The last open issues have been addressed, so it is time to move
this out of staging and into the mainline and to move the public
cec headers to include/uapi/linux.
Signed-off-by: Hans Verkuil
---
drivers/media/Kconfig | 16
drivers/media
From: Hans Verkuil
CDC-Only CEC devices are CEC devices that can only handle CDC messages,
all other messages are ignored.
Add a flag to signal that this is a CDC-Only device and act accordingly.
Also add helper functions to identify if a CEC device is configured as a
CDC-Only device, a second
From: Hans Verkuil
Give the caller more control over how replies to a transmit are
handled. By default the reply will only go to the filehandle that
called CEC_TRANSMIT. If this new flag is set, then the reply will
also go to all followers.
Signed-off-by: Hans Verkuil
---
Documentation/media/u
From: Hans Verkuil
By default the CEC_MSG_USER_CONTROL_PRESSED/RELEASED messages
are passed on to the follower(s) only. If the new
CEC_LOG_ADDRS_FL_ALLOW_RC_PASSTHRU flag is set in the
flags field of struct cec_log_addrs then these messages are also
passed on to the remote control input subsystem
With the new dma_request_chan() the client driver does not need to look for
the DMA resource and it does not need to pass filter_fn anymore.
By switching to the new API the driver can now support deferred probing
against DMA.
Signed-off-by: Peter Ujfalusi
CC: Laurent Pinchart
CC: Mauro Carvalho
-Shyti/Add-support-for-IR-transmitters/20161102-184657
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make
On Wed, 24 Aug 2016, Markus Heiser wrote:
> From: Markus Heiser
>
> This extends the method to build only sub-folders to the targets
> "latexdocs" and "pdfdocs". To do so, a conf.py in the sub-folder is
> required, where the latex_documents of the sub-folder are
> defined. E.g. to build only gpu'
Move the input device allocation, map and protocol handling to
different functions.
Signed-off-by: Andi Shyti
---
drivers/media/rc/rc-main.c | 143 +
1 file changed, 81 insertions(+), 62 deletions(-)
diff --git a/drivers/media/rc/rc-main.c b/drivers/m
Raw IR transmitters do not need any thread listening for
occurring events. Check the driver type before running the
thread.
Signed-off-by: Andi Shyti
---
drivers/media/rc/rc-ir-raw.c | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/drivers/media/rc/rc-ir-raw
Document the ir-spi driver's binding which is a IR led driven
through the SPI line.
Signed-off-by: Andi Shyti
---
.../devicetree/bindings/leds/spi-ir-led.txt| 29 ++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/spi-ir-led
The driver type can be assigned immediately when an RC device
requests to the framework to allocate the device.
This is an 'enum rc_driver_type' data type and specifies whether
the device is a raw receiver or scancode receiver. The type will
be given as parameter to the rc_allocate_device device.
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its func
Hi,
The main goal is to add support in the rc framework for IR
transmitters, which currently is only supported by lirc but that
is not the preferred way.
The last patch adds support for an IR transmitter driven by
the MOSI line of an SPI controller, it's the case of the Samsung
TM2(e) board which
IR raw transmitter driver type is specified in the enum
rc_driver_type as RC_DRIVER_IR_RAW_TX which includes all those
devices that transmit raw stream of bit to a receiver.
The data are provided by userspace applications, therefore they
don't need any input device allocation, but still they need
On 2.11.2016 10:15, Pavel Machek wrote:
Hi!
I'll have to go through the patches, et8ek8 driver is probably not
enough to get useful video. platform/video-bus-switch.c is needed for
camera switching, then some omap3isp patches to bind flash and
autofocus into the subdevice.
Then, device tree
Hi!
> >>I'll have to go through the patches, et8ek8 driver is probably not
> >>enough to get useful video. platform/video-bus-switch.c is needed for
> >>camera switching, then some omap3isp patches to bind flash and
> >>autofocus into the subdevice.
> >>
> >>Then, device tree support on n900 can b
85 matches
Mail list logo
