summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* h1lcb defconfig config build autofs4 and fuse as modulesbaserock/renesas/rcar-h1-20130604REA2013-06-111-0/+2
|
* h1lcb defconfig af-bus enableREA2013-06-111-0/+6
|
* netfilter: add netfilter D-Bus moduleAlban Crequy2013-06-116-0/+525
| | | | | | | | | | AF_BUS has netfilter hooks on the packet sending path. This allows the netfilter subsystem to register netfilter hook handlers. The netfilter_dbus module allows to inspect D-Bus messages and take actions based on the information contained on these messages. Signed-off-by: Alban Crequy <alban.crequy@collabora.co.uk>
* netfilter: nfdbus: Add D-bus match rule implementationJavier Martinez Canillas2013-06-112-0/+1213
| | | | | | | | | | The D-Bus netfilter module needs to decode D-Bus match rules to decide if a given peer can receive or not a D-Bus message. Add a match rule implementation to be used by the netfilter D-Bus module. Based on a previous patch by Alban Crequy. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* netfilter: nfdbus: Add D-bus message parsingJavier Martinez Canillas2013-06-112-0/+265
| | | | | | | | | | The netfilter D-Bus module needs to parse D-bus messages sent by applications to decide whether a peer can receive or not a D-Bus message. Add D-bus message parsing logic to be able to analyze. Based on a previous patch by Alban Crequy. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* netlink: connector: Add idx and val identifiers for netfilter D-BusJavier Martinez Canillas2013-06-111-1/+3
| | | | | | | | | | | | | | | | The D-bus IPC system implements a transport that uses AF_BUS sockets to send D-Bus messages to the peers. This allows decouple the routing logic from the daemon and move it to the kernel which has the advantage of reducing the number of context switches and the messages copied to user-space. A D-Bus protocol aware netfilter module decide which peer can recive a given message based on a set of D-Bus match rules. These match rules are set from user-space using the netlink connector API. Based on a previous patch by Alban Crequy. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* netlink: connector: implement cn_netlink_replyAlban Crequy2013-06-112-0/+33
| | | | | | | | | | | | | | | | | | | | | | In a connector callback, it was not possible to reply to a message only to a sender. This patch implements cn_netlink_reply(). It uses the connector socket to send an unicast netlink message back to the sender. The following pseudo-code can be used from a connector callback: struct cn_msg *cn_reply; cn_reply = kzalloc(sizeof(struct cn_msg) + sizeof(struct ..._nl_cfg_reply), GFP_KERNEL); cn_reply->id = msg->id; cn_reply->seq = msg->seq; cn_reply->ack = msg->ack + 1; cn_reply->len = sizeof(struct ..._nl_cfg_reply); cn_reply->flags = 0; rr = cn_netlink_reply(cn_reply, nsp->pid, GFP_KERNEL); Signed-off-by: Alban Crequy <alban.crequy@collabora.co.uk>
* net: bus: Add the AF_BUS socket address family to KBuildJavier Martinez Canillas2013-06-114-0/+24
| | | | | | This patch adds the AF_BUS code to the Linux Kernel build system. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* net: bus: Add garbage collector for AF_BUS sockets.Javier Martinez Canillas2013-06-111-0/+322
| | | | | | This patch adds a garbage collector for AF_BUS sockets. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* net: bus: Add implementation of Bus domain socketsJavier Martinez Canillas2013-06-111-0/+2688
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each process connected to an AF_BUS socket, has one or more addresses within that bus. These addresses are 64-bit unsigned integers, interpreted by splitting the address into two parts: the most significant 16 bits are a prefix identifying the type of address, and the remaining 48 bits are the actual client address within that prefix. The process that calls bind(2) on the socket is the owner of the bus and is called the bus master. The master is a special client of the bus and has some responsibility for the bus' operation. The master is assigned a fixed address with all the bits zero. The prefix with all bits zero is reserved for use by the kernel, which automatically assigns one address from this prefix to each client on connection. The address in this prefix with all bits zero is always assigned to the bus master. Addresses on the prefix 0000 are unique and will never repeat for the lifetime of the bus master. AF_BUS transport can support two network topologies. When a process first connect to the bus master, it can only communicate with the bus master. The process can't send and receive packets from other peers on the bus. So, from the client process point of view the network topology is point-to-point. The bus master can allow the connected peer to be part of the bus and start to communicate with other peers by setting an socket option with the setsockopt(2) system call using the accepted socket descriptor. At this point, the topology becomes a bus to the client process. Packets whose destination address is not assigned to any client are routed by default to the bus master (the client accepted socket descriptor). Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* scm: allow AF_BUS sockets to send ancillary dataJavier Martinez Canillas2013-06-111-1/+2
| | | | | | | | | | | | | UNIX domain sockets support passing file descriptors or process credentials in the form of ancillary data. Since AF_BUS sockets are used to communicate processes on a local machine, they should also support passing control messages. The core socket level control messages processing only allows sockets whose family is PF_UNIX to send SCM_RIGHTS type messages. So, let's also allow to PF_BUS sockets. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* netfilter: add NFPROTO_BUS hook constant for AF_BUS socket familyJavier Martinez Canillas2013-06-111-0/+1
| | | | | | | AF_BUS sockets add a netfilter NF_HOOK() on the packet sending path. This allows packet to be mangled by registered netfilter hooks. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* security: selinux: Add AF_BUS socket SELinux hooksJavier Martinez Canillas2013-06-111-0/+35
| | | | | | Add Security-Enhanced Linux (SELinux) hook for AF_BUS socket address family. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* security: Add Linux Security Modules hook for AF_BUS socketsJavier Martinez Canillas2013-06-113-0/+25
| | | | | | | AF_BUS implements a security hook bus_connect() to be used by LSM to enforce connectivity security policies. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* net: bus: add af_bus address and af_bus socket address definitionsJavier Martinez Canillas2013-06-112-0/+307
| | | | | | | | | | | | | | | | An AF_BUS socket can have many addresses associated. This allows to send multicast packets on different domains. An af_bus address is an unsigned 64-bit value that contains two fields: a 16-bit prefix and a 48-bit client address. Each bus has an associated path name that uniquely identifies the bus. So, a socket address is composed of the bus path and the peer address. Clients can send unicast packets to each other and multicast to different prefixes but they can only connect(2) to a special socket that owns the bus an is known as the bus master. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* net: bus: Add AF_BUS documentationJavier Martinez Canillas2013-06-111-0/+558
| | | | | | | AF_BUS is different to other POSIX BSD sockets address families so a is good to have a documentation about its design, ABI and semantics. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* net: bus: add the AF_BUS socket address familyJavier Martinez Canillas2013-06-112-4/+7
| | | | | | | | | | | | | AF_BUS is a new socket address family that allows both unicast and multicast I on a local machine with total ordering for messages (every process on the same bus sees each message in the same order). A process can create buses to which other processes can connect and communicate with each other by sending messages. Processes' addresses are automatically assigned by the bus on connect and are unique. Messages can be sent either to process' unique address or to a bus multicast address. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
* h1lcb enable bluetoothREA2013-06-111-1/+13
|
* h1lcb change IRQ1 pin for boards with series number above 15REA2013-06-113-0/+11
|
* h1lcb spi setup dma channelsREA2013-06-113-0/+52
|
* h1lcb spi change platform dev configREA2013-06-111-0/+24
|
* h1lcb spi change to interrupt and dma transfer supportREA2013-06-112-76/+422
|
* h1lcb fb fix 1024x600 resolution on Xenarc monitorREA2013-06-111-1/+1
|
* h1lcb enable DU1 and hdmi tfp410 on DU1REA2013-06-111-32/+0
|
* h1lcb enable hdmi tfp410 on DU0REA2013-06-111-2/+0
|
* ARM: shmobile: r8a7779: h1lcbREA2013-06-117-4/+1340
|
* ARM: shmobile: Add PCIe setup to r8a7779 devicePhil Edworthy2013-06-111-0/+25
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ARM: shmobile: Add R-Car PCIe driverPhil Edworthy2013-06-115-0/+876
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ARM: pci: Add Renesas PCI ID for R-Car root complex devicesPhil Edworthy2013-06-111-0/+1
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ARM: shmobile: r8a7779: Add PCIe clocksPhil Edworthy2013-06-111-1/+3
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* libata-sff: Fix use of IO memPhil Edworthy2013-06-111-2/+2
| | | | | | | PCI requires IO mem, but not an IO port. Some of the SFF code did not make this distinction. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* rcarvin: Add error message if SoC camera doesn't have g_mbus_fmt fn.Phil Edworthy2013-06-111-1/+4
| | | | | | | | The VIN driver requires that tha SoC camera driver implements the g_mbus_fmt function. If it doesn't, users won't get a useful message. Hence this additional error message. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ASoC: rcar: Fix output format for ak4643 codec on Marzen boardPhil Edworthy2013-06-111-1/+1
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ASoC: rcar: Fix output format for ak4648 codec on Hurricane boardPhil Edworthy2013-06-111-1/+1
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ASoC: rcar: New glue code for ak4648 codec on Hurricane boardPhil Edworthy2013-06-113-4/+165
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ASoC: rcar: Add ak4642 on SSI7/8Phil Edworthy2013-06-111-11/+54
| | | | | | | | The SRU driver uses somewhat hard coded information about the SSI channels connected to the audio codec. This change adds support for SSI7 and SSI8 connected to an ak4642 audio codec. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ARM: shmobile: Add DMA config for audio SSI7 and SSI8Phil Edworthy2013-06-112-0/+20
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ARM: shmobile: r8a7779: hurricane: Add option to use 10-bit camerasPhil Edworthy2013-06-112-0/+30
| | | | | | | | | | The ov10635 cameras can output 8 or 10-bit BT.656 data. By default they use 8-bit data. This change allows the user to select 10-bit data. Note: only VIN0 and VIN1 on the R-Car H1 support 10-bit YUV data. Due to pinmux conflicts with VIN1, you can no longer use VIN3. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ARM: shmobile: r8a7779: hurricaneJames Gomez2013-06-116-1/+1346
| | | | | | Added support for the R-Car H1 hurricane platform. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: defconfig: Enable I2C driver interfacePhil Edworthy2013-06-111-0/+1
| | | | | | By default, enable device nodes for I2C devices. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ov10635: Fix analogue timing for 1280x800@30fpsPhil Edworthy2013-06-111-1/+1
| | | | | | | At 1280x800 at 30fps, the timings previously used do not work. This change increases the HTS setting to fix it. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: Add pinmux for additional serial channelsPhil Edworthy2013-06-111-0/+12
| | | | | | Add pinmux for SCIF0, SCIF1 and SCIF3. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: Add resources & pinmux for 24-bit RGB Video In (VIN0)Phil Edworthy2013-06-112-0/+40
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* rgb 24-bit SoC camera 'dummy' driverPhil Edworthy2013-06-114-0/+265
| | | | | | | This driver does little other than tell the SoC bridge hardware what the output format is. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: defconfig for REE-EDC Expansion BoardPhil Edworthy2013-06-111-0/+3
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: Add second display unitPhil Edworthy2013-06-111-1/+69
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: Add on-chip ethernet devicePhil Edworthy2013-06-111-0/+98
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: Use ov10635 cameras on vin1 and vin3Phil Edworthy2013-06-111-11/+19
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* marzen: Add ov10635 cameras on vin0 and vin2Phil Edworthy2013-06-111-3/+73
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
* ov10635: Add support for 10-bit BT.656 outputPhil Edworthy2013-06-111-15/+55
| | | | Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
View Lorry Controller Status