| /linux-4.1.27/drivers/pinctrl/intel/ |
| D | pinctrl-intel.c | 113 struct intel_community *community; in intel_get_community() local
117 community = &pctrl->communities[i]; in intel_get_community()
118 if (pin >= community->pin_base && in intel_get_community()
119 pin < community->pin_base + community->npins) in intel_get_community()
120 return community; in intel_get_community()
130 const struct intel_community *community; in intel_get_padcfg() local
133 community = intel_get_community(pctrl, pin); in intel_get_padcfg()
134 if (!community) in intel_get_padcfg()
137 padno = pin_to_padno(community, pin); in intel_get_padcfg()
138 return community->pad_regs + reg + padno * 8; in intel_get_padcfg()
[all …]
|
| D | pinctrl-cherryview.c | 179 const struct chv_community *community; member
694 return pctrl->community->ngroups; in chv_get_groups_count()
702 return pctrl->community->groups[group].name; in chv_get_group_name()
710 *pins = pctrl->community->groups[group].pins; in chv_get_group_pins()
711 *npins = pctrl->community->groups[group].npins; in chv_get_group_pins()
759 return pctrl->community->nfunctions; in chv_get_functions_count()
767 return pctrl->community->functions[function].name; in chv_get_function_name()
777 *groups = pctrl->community->functions[function].groups; in chv_get_function_groups()
778 *ngroups = pctrl->community->functions[function].ngroups; in chv_get_function_groups()
790 grp = &pctrl->community->groups[group]; in chv_pinmux_set_mux()
[all …]
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 1.Intro | 4 work with the development community with a minimum of frustration. It is
5 an attempt to document how this community works in a way which is
19 availability to users, community support in many forms, and the ability to
31 involving the development community as soon as possible.
39 taken seriously by the development community, patches must be properly
87 Working with the kernel development community is not especially hard. But,
89 difficulties when trying to do kernel work. The kernel community has
99 community's ways (or, worse, who tries to flout or circumvent them) will
100 have a frustrating experience in store. The development community, while
107 community is always in need of developers who will help to make the kernel
[all …]
|
| D | 3.Early-stage | 27 immediate problem. To the wider kernel community, though, it was seen as a
34 The audio community, however, could not see past the particular solution
51 - and to discuss it with the development community before investing in the
70 discussions with the community before launching into implementation. Early
90 Years of experience with the kernel development community have taught a
93 released into the community. Sometimes these problems are severe,
95 the kernel community's standards. Some examples include:
163 provide can help the development community provide useful input on the
179 community informed as you go.
|
| D | 2.Process | 34 community) is merged into the mainline kernel. The bulk of changes for a
150 done without involving the community, but it is better to do this work
187 leave a poor impression in the development community. Merging code
335 community is git. Git is one of a number of distributed version control
336 systems being developed in the free software community. It is well tuned
374 lists. It is hard to be a fully-functioning member of the community
393 development community comes together as a whole; developers who avoid this
459 noise which is distracting for the development community as a whole, so,
461 introduce themselves to the community will not get the sort of reception
478 building respect with the rest of the development community.
|
| D | 6.Followthrough | 14 kernel community to ensure that your code is up to the kernel's quality
94 kernel development community; he can often unjam a situation which seems to
118 contents visible to the development community as a whole. At this point,
174 development community remembers developers who lose interest in their code
205 be hurtful and discouraging, but the community will remember your reaction
|
| D | 5.Posting | 4 the community for review and, eventually, inclusion into the mainline
5 kernel. Unsurprisingly, the kernel development community has evolved a set
19 feedback from the community before the work is complete. So you should
33 sending patches to the development community. These include:
76 out how to do it in the way that the community expects. There are a few
|
| D | 4.Coding | 3 While there is much to be said for a solid and community-oriented design
45 pure coding style fixes are seen as noise by the development community;
|
| /linux-4.1.27/tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 35 https://help.ubuntu.com/community/KVM/CreateGuests
36 https://help.ubuntu.com/community/JeOSVMBuilder
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/omap/ |
| D | omap.txt | 106 - OMAP3 BeagleBoard : Low cost community board
115 - OMAP4 PandaBoard : Low cost community board
133 - AM335X Bone : Low cost community board
|
| /linux-4.1.27/Documentation/ |
| D | HOWTO | 6 to work with the Linux kernel development community. It tries to not
22 and hints on how to work with the community. It will also try to
23 explain some of the reasons why the community works like it does.
47 existing development community. It is a diverse group of people, with
74 invaluable for learning how to interact with the kernel community. When
188 some task to start doing to join into the kernel development community,
419 Working with the community
422 The goal of the kernel community is to provide the best possible kernel
445 In a community that is looking for the best technical solution possible,
459 Differences between the kernel community and corporate structures
[all …]
|
| D | vgaarbiter.txt | 179 with the Xorg community in 2005 [1, 2]. In the end of 2007, Paulo Zanoni and
|
| D | kernel-docs.txt | 682 Keywords: linux, community, everything!
|
| /linux-4.1.27/drivers/staging/ozwpan/ |
| D | TODO | 9 - code review by USB developer community.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ncpfs.txt | 3 similar to the NFS used in the TCP/IP community.
|
| D | proc.txt | 60 chapters, it seems only fair to give the work back to the Linux community.
|
| /linux-4.1.27/drivers/net/ |
| D | LICENSE.SRC | 13 of ideas throughout the research community. All software is furnished
|
| /linux-4.1.27/Documentation/scsi/ |
| D | lpfc.txt | 45 The community supporting kernel.org has driven an effort to remove
54 community in modifying the behavior of the SCSI midlayer so that SCSI
|
| D | FlashPoint.txt | 18 "Mylex is committed to supporting the Linux community," says Peter Shambora,
73 been problematic for members of the Linux community, in that no Linux
99 publicly about BusLogic's attitude toward the Linux community, and I felt
119 SCSI solution for the Linux community, and does not want to see anyone left
|
| D | BusLogic.txt | 59 products to the Linux community. In November 1995, I was offered the
64 readily achieve, and the Linux community has available high performance host
69 potential of the Linux community.
72 Linux community, and I am now working on a Linux driver for the DAC960 PCI RAID
|
| D | ChangeLog.megaraid | 91 Fix: A patch submitted to community from following folk.
|
| /linux-4.1.27/drivers/staging/ |
| D | Kconfig | 14 affect support options from both the community, and various
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | AUTHORS | 47 Thanks to those in the community who have submitted detailed bug reports
|
| /linux-4.1.27/Documentation/vm/ |
| D | zswap.txt | 27 been identified in prior community discussions.
|
| /linux-4.1.27/Documentation/usb/ |
| D | CREDITS | 155 - All the Free Software and Linux community, the FSF & the GNU
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 280 the device property has been accepted by the Linux community, it must be
450 are not UEFI members, many other members of the Linux community are and would
|
| D | acpi_object_usage.txt | 398 by the kernel community, then register it with the
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 595 have made the drive's support available to the \linux\ community. The
688 \linux\ community, and not from some standardizing institute. What
708 community. All the CD-player authors will have to be informed, we can
|
| /linux-4.1.27/drivers/net/usb/ |
| D | Kconfig | 430 used by most of the ARM Linux community with device controllers
|
| /linux-4.1.27/ |
| D | MAINTAINERS | 331 W: http://ez.analog.com/community/linux-device-drivers
338 W: http://ez.analog.com/community/linux-device-drivers
345 W: http://ez.analog.com/community/linux-device-drivers
352 W: http://ez.analog.com/community/linux-device-drivers
359 W: http://ez.analog.com/community/linux-device-drivers
396 W: http://ez.analog.com/community/linux-device-drivers
407 W: http://ez.analog.com/community/linux-device-drivers
415 W: http://ez.analog.com/community/linux-device-drivers
442 W: http://ez.analog.com/community/linux-device-drivers
678 W: http://ez.analog.com/community/linux-device-drivers
[all …]
|
| D | CREDITS | 3641 D: AIPS port, astronomical community support.
|
| /linux-4.1.27/Documentation/security/ |
| D | Smack.txt | 314 community. There are also some terms from Linux that are likely to crop up:
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | memory.txt | 850 commented and discussed quite extensively in the community.
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1119 the speakup community. We would like to thank him for his work on the
1148 Charles Hallenbeck, another member of the speakup community, wrote the
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 4379 which is a great way of keeping the UML user community on top of
|